{"version":"2.1.295","anchor":"tengu-modular-mochi-now-takes-the-mcp-client-list","canonical_anchor":"tengu-modular-mochi-now-takes-the-mcp-client-list","heading":"Destructive MCP tool check now also looks at the session's MCP servers","tier":"notice","area":"Auto Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/tengu-modular-mochi-now-takes-the-mcp-client-list","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Destructive MCP tool check now also looks at the session's MCP servers\n\nThe flag-controlled check for destructive MCP tool calls in remote auto mode now also takes the session's MCP servers into account\n\n**What**\n\nThe check behind the `tengu_modular_mochi` flag, one of the ways Claude Code decides whether destructive MCP tool calls are allowed in remote auto mode, now also receives the list of MCP servers connected to the session when deciding. MCP servers are outside programs that give Claude Code extra tools. The flag is still required, and it is off unless it is switched on remotely.\n\nThe flag server has returned on for this site's account and for an anonymous one, though not yet read under this release.\n\n**Why**\n\nWhether this check passes can now depend on which MCP servers your session has connected.\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.295; 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- Area: Auto Mode\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}