{"version":"2.1.299","anchor":"new-disallow-tools-option-in-a-case-runner-cli-command","canonical_anchor":"new-disallow-tools-option-in-a-case-runner-cli-command","heading":"New --disallow-tools option for running case files","tier":"use","area":"Plugin Evals","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/new-disallow-tools-option-in-a-case-runner-cli-command","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### New `--disallow-tools` option for running case files\n\nA command that runs case files gains `--disallow-tools`, which keeps chosen built-in tools from Claude in every case\n\n**Unclear.** It is not clear which command this is or whether it is available to everyone.\n\n**What**\n\nA command that runs case files, and that also has a `--scaffold` option, gains `--disallow-tools <tools...>`. It names built-in tools to keep from Claude in every case, even if they are granted, for example `Agent TaskStop`.\n\n**Why**\n\nPeople running evaluations can block certain tools for a whole run without editing each case.\n\n- Area: Plugin Evals\n- Names: `--disallow-tools`, `--scaffold`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}