{"version":"2.1.309","anchor":"chrome-extension-blocked-by-policy-notice-and-mcp-server-adm","canonical_anchor":"chrome-extension-blocked-by-policy-notice-and-mcp-server-adm","heading":"Built-in Chrome server left out of the policy-blocked MCP server warning","tier":"notice","area":"MCP","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/chrome-extension-blocked-by-policy-notice-and-mcp-server-adm","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Built-in Chrome server left out of the policy-blocked MCP server warning\n\nThe warning about MCP servers blocked by policy no longer lists the built-in Chrome server when Claude Code handles it separately\n\n**What**\n\nMCP servers are add-on tool providers that Claude Code can connect to. MCP stands for Model Context Protocol. When your organization's policy blocks some of them, Claude Code shows a warning that lists the blocked servers. That warning no longer includes the built-in Chrome server when Claude Code handles that server separately. Before, every blocked server was listed.\n\nThe filter that decides which servers are let through also allows servers whose address (`url`) passes a new check.\n\n**Why**\n\nYou see fewer warnings about a server you did not set up yourself.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}