{"version":"2.1.222","anchor":"destructive-mcp-tools-can-be-included-in-remote-auto-mode","canonical_anchor":"destructive-mcp-tools-can-be-included-in-remote-auto-mode","heading":"Destructive MCP tools can be included in remote auto-mode","tier":"soon","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222\/e\/destructive-mcp-tools-can-be-included-in-remote-auto-mode","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222","markdown":"### Destructive MCP tools can be included in remote auto-mode\n\nDestructive MCP tools could stop skipping permission prompts in remote auto mode, but that is off.\n\n**What**\n\nA new predicate combines the auto\/plan remote mode check with a tool's isDestructive result, so destructive MCP tools still get a permission prompt. It is off in this build.\n\n**Details**\n\n- When on, an MCP ask-override no longer exempts destructive tools from the prompt.\n- Gated on tengu_remote_auto_mode_include_destructive_mcp, fallback value in source is false.\n- A new mcpServerAskOverride field was added to four permission telemetry payloads.\n\n**Evidence**\n\n`tengu_remote_auto_mode_include_destructive_mcp`\n\n- Flag `tengu_remote_auto_mode_include_destructive_mcp`: Off in both readings (read for one account on one subscription tier against v2.1.222; this account: off, anonymous baseline: off, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Permissions\n- Names: `tengu_remote_auto_mode_include_destructive_mcp`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}