{"version":"2.1.286","anchor":"mcp-server-policy-bypass-exemption-gate-unchanged-but-presen","canonical_anchor":"mcp-server-policy-bypass-exemption-gate-unchanged-but-presen","heading":"No behaviour change to MCP policy exemptions in remote bypass mode","tier":"internal","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/mcp-server-policy-bypass-exemption-gate-unchanged-but-presen","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### No behaviour change to MCP policy exemptions in remote bypass mode\n\nThe rule that exempts MCP server policy denials in remote bypass-permissions sessions behaves the same as before\n\n**What**\n\nThis rule concerns remote sessions (`CLAUDE_CODE_REMOTE`) running in `bypassPermissions` mode, where Claude Code acts without asking permission. In those sessions, denials from the MCP server policy can be exempted when `tengu_mcp_server_policy_bypass_exempt` is on. Its built-in default is on unless it is switched off remotely. MCP servers are outside programs that give Claude Code extra tools.\n\nOnly internal names in this code changed. The logic is the same.\n\n**Why**\n\nIn practice, nothing is different for users.\n\n- Flag `tengu_mcp_server_policy_bypass_exempt`: Not enough to say (read for one account on one subscription tier against v2.1.286; this account: no value returned, anonymous baseline: no value returned, compiled default: on) 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: MCP\n- Names: `CLAUDE_CODE_REMOTE`, `bypassPermissions`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}