{"version":"2.1.273","anchor":"mcp-server-allowdeny-list-computation-refactored-into-named","canonical_anchor":"mcp-server-allowdeny-list-computation-refactored-into-named","heading":"MCP server allow\/deny-list computation refactored into named helpers","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/mcp-server-allowdeny-list-computation-refactored-into-named","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### MCP server allow\/deny-list computation refactored into named helpers\n\nInternal code for computing which MCP servers are allowed or blocked was reorganized into separate functions\n\n**What**\n\nThe logic that determines which MCP servers (external tool integrations) are allowed or denied based on policy settings was split into three separate internal functions: one for computing allowed servers (respecting managed-hooks-only style policy), one for computing denied servers (deduplicated across managed settings sources), and one for combining all these inputs into a single hash.\n\n**Why**\n\nThis is an internal refactor of how the `allowedMcpServers` allowlist setting, which controls which MCP servers users can add, is computed. It does not change the setting's behavior for users.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}