{"version":"2.1.290","anchor":"control-request-set-mcp-permission-mode-override-gains-askfo","canonical_anchor":"control-request-set-mcp-permission-mode-override-gains-askfo","heading":"Programs hosting Claude Code can force named MCP tools to ask permission","tier":"use","area":"SDK","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/control-request-set-mcp-permission-mode-override-gains-askfo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Programs hosting Claude Code can force named MCP tools to ask permission\n\nA host can now list tools that must always ask before running, even ones that would normally allow themselves\n\n**What**\n\nApps that embed Claude Code control it by sending it requests. The `set_mcp_permission_mode_override` request now accepts an `askForTools` list when the mode is `default`. Any tool named in that list will ask for permission before running, even if it would otherwise allow itself to run.\n\nRight now the only tools that allow themselves are Claude in Chrome's safe tools that run without asking.\n\n**Why**\n\nHosts get finer control over which tools from MCP servers, the outside programs that give Claude Code extra tools, can run without asking.\n\n- Area: SDK\n- Names: `set_mcp_permission_mode_override`, `askForTools`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: no"}