{"version":"2.1.267","anchor":"session-can-now-run-with-built-in-tools-entirely-disabled-a","canonical_anchor":"session-can-now-run-with-built-in-tools-entirely-disabled-a","heading":"Session can now run with built-in tools entirely disabled, and plugins are blocked from adding tools in that mode","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/session-can-now-run-with-built-in-tools-entirely-disabled-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Session can now run with built-in tools entirely disabled, and plugins are blocked from adding tools in that mode\n\nSessions can now run with all built-in tools disabled, and plugins are blocked from adding tools back in that mode\n\n**What**\n\nWhen `--allowedTools` is given but doesn't match any known built-in tool, Claude Code now recognizes this as a session with built-in tools entirely disabled, and passes that state through its permission logic. Plugins are explicitly blocked from registering any of their own tools in that case.\n\n**Why**\n\nThis closes a gap where a session set up to disable all built-in tools (via `--tools \"\"`) could still end up with tools available if a plugin added its own, ensuring the restriction is fully enforced.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}