{"version":"2.1.299","anchor":"cloudheadless-session-config-accepts-disallowed-tools","canonical_anchor":"cloudheadless-session-config-accepts-disallowed-tools","heading":"Cloud and headless runs can list tools to block","tier":"use","area":"Headless Mode","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/cloudheadless-session-config-accepts-disallowed-tools","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Cloud and headless runs can list tools to block\n\nThe configuration for cloud and headless runs now accepts an optional `disallowed_tools` list next to `allowed_tools`\n\n**Unclear.** Whether Claude Code actually blocks the tools named in `disallowed_tools` is not shown, only that the setting is accepted.\n\n**What**\n\nThe configuration used for cloud and headless runs (sessions that run without you typing into a terminal) already accepted `timeout_seconds` and `allowed_tools`. It now also accepts `disallowed_tools`, an optional list of tool names. Tools are the actions Claude can take, such as reading files or running commands.\n\n**Why**\n\nA request to start one of these runs can now name tools to deny outright, rather than only listing the tools that are allowed.\n\n- Area: Headless Mode\n- Names: `disallowed_tools`, `allowed_tools`, `timeout_seconds`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: no"}