{"version":"2.1.259","anchor":"new-destructive-mcp-auto-mode-gate-added-alongside-the-exist","canonical_anchor":"new-destructive-mcp-auto-mode-gate-added-alongside-the-exist","heading":"New destructive-MCP auto-mode gate added alongside the existing one","tier":"internal","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259\/e\/new-destructive-mcp-auto-mode-gate-added-alongside-the-exist","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259","markdown":"### New destructive-MCP auto-mode gate added alongside the existing one\n\nDestructive MCP calls under remote auto mode can now be allowed by either the existing gate or a new flag.\n\nWhether destructive MCP tool calls are allowed under remote auto mode is now decided by either of two checks: the existing gate, or a new one controlled by the `tengu_modular_mochi` flag.\n\n- Flag `tengu_modular_mochi`: Off by default, switched on for this account (read for one account on one subscription tier against v2.1.259; this account: on, anonymous baseline: on, 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- Flag `tengu_remote_auto_mode_include_destructive_mcp`: Off in both readings (read for one account on one subscription tier against v2.1.259; 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_modular_mochi`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}