{"version":"2.1.302","anchor":"one-mcp-served-tool-bypasses-the-isenabled-check","canonical_anchor":"one-mcp-served-tool-bypasses-the-isenabled-check","heading":"One tool is no longer refused when switched off in Claude Code's tool server","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/one-mcp-served-tool-bypasses-the-isenabled-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### One tool is no longer refused when switched off in Claude Code's tool server\n\nWhen Claude Code serves its tools to other programs, one specific tool now skips the \"switched off in this server\" refusal\n\n**Unclear.** It is not clear which tool is exempt from the refusal.\n\n**What**\n\nClaude Code can act as a tool server, offering its own tools to another program. Before running a tool that way, it checks whether the tool is switched on. In the previous build, every switched-off tool was refused with the message \"was not run: it is switched off in this server. Retrying won't help.\" That refusal now applies to every tool except one, which is checked and allowed through even when it is switched off.\n\n**Why**\n\nThis is an exception in the path that decides which tools a server-side caller can run. If you rely on Claude Code refusing switched-off tools, one tool now behaves differently.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}