{"version":"2.1.248","anchor":"mcp-server-allow-and-deny-lists-get-settings-keys","canonical_anchor":"mcp-server-allow-and-deny-lists-get-settings-keys","heading":"MCP server allow and deny lists get settings keys","tier":"use","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/mcp-server-allow-and-deny-lists-get-settings-keys","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### MCP server allow and deny lists get settings keys\n\nYou can allow or block specific MCP servers with allowedMcpServers and deniedMcpServers settings.\n\n**What**\n\nTwo settings keys, `allowedMcpServers` and `deniedMcpServers`, are now paired with validation schemas in a table, so MCP servers can be permitted or blocked from settings files.\n\n**Details**\n\n- New arrays group the settings tiers: `policySettings`, `flagSettings` and `userSettings` on one side, `localSettings` and `projectSettings` on the other, with a map labelling the first three `policy`, `flag` and `user`.\n- A separate map ties the decisions `allow`, `deny` and `ask` to the rule lists `alwaysAllowRules`, `alwaysDenyRules` and `alwaysAskRules`.\n\n**Evidence**\n\n`{ key: \"allowedMcpServers\", schema: tzt }`\n\n- Area: MCP\n- Names: `allowedMcpServers`, `deniedMcpServers`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 4\/5"}