{"version":"2.1.321","anchor":"mcp-server-policy-rules-now-merged-through-a-shared-helper","canonical_anchor":"mcp-server-policy-rules-now-merged-through-a-shared-helper","heading":"MCP server policy rules are now combined in one shared step","tier":"internal","area":"MCP","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/mcp-server-policy-rules-now-merged-through-a-shared-helper","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### MCP server policy rules are now combined in one shared step\n\nClaude Code now builds its MCP server policy rules through a single shared merge step\n\n**Unclear.** It is not clear whether the shared merge step makes allow, deny or ask decisions behave differently.\n\n**What**\n\nMCP servers are add-ons that give Claude Code extra tools. Organizations can set policy rules that allow, deny or ask before using them. Claude Code used to build those allow, deny and ask rules separately. It now builds them through one shared step that merges them into the existing rules.\n\n**Why**\n\nThis could affect how an organization's MCP rules are enforced.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: org\n- Heads-up: no"}