--disallow-tools
A Claude Code CLI flag, read out of the shipped bundle. It has been in the build since v2.1.299, including the newest one read.
A command that runs case files gains --disallow-tools, which keeps chosen built-in tools from Claude in every case
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.299.
In the changelogs
2Releases whose published page names --disallow-tools.
-
v2.1.299
New
--disallow-toolsoption for running case filesA command that runs case files gains
--disallow-tools, which keeps chosen built-in tools from Claude in every casefound in this entry's text, named in this entry
-
v2.1.299
Plugin evals can now take tools away from Claude with --disallow-tools
The plugin eval runner accepts
--disallow-toolsand a per-casedisallowed_toolslist, and scores runs that end on an API error as 0found in this entry's text, named in this entry
First cited
2The earliest release whose published evidence quoted --disallow-tools was v2.1.299, 14 Oct 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.
Presence across releases
1Build by build
10One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the CLI flag does. All CLI flags.