{"version":"2.1.268","anchor":"mcp-client-bridge-gains-a-global-isdisabled-kill-switch-ch","canonical_anchor":"select-browser-mcp-tool-can-now-be-explicitly-disabled-and","heading":"Browser MCP tools gain a global isDisabled kill-switch","tier":"notice","area":"Chrome & Browser","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/mcp-client-bridge-gains-a-global-isdisabled-kill-switch-ch","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Browser MCP tools gain a global isDisabled kill-switch\n\nBrowser-control tools like switch_browser, list_connected_browsers, and select_browser now check a kill-switch before acting\n\n**What**\n\nThe Chrome\/browser MCP tool-call path now checks `isDisabled?.()` before doing any work, across dispatch, `tabs_context` lookup, `switch_browser`, `list_connected_browsers`, `select_browser`, connection watchers, and tool listing. When it's disabled:\n\n- `list_connected_browsers` returns `Unknown tool: list_connected_browsers` instead of running.\n\n- `switch_browser` and the computer-use 'type' action return a disabled\/'Unknown tool' response instead of proceeding.\n\n- `select_browser` returns `Unknown tool: select_browser`; its success message also changed from 'Connected to browser' to 'Selected browser'.\n\n**Why**\n\nThis gives Claude Code a single, central way to turn off browser-control tools entirely (for example, in an environment where automated browser control shouldn't be available) rather than needing each tool to fail in its own way.\n\n- Area: Chrome & Browser\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}