{"version":"2.1.321","anchor":"claude-in-chrome-org-policy-enforced-on-mcp-tool-refresh","canonical_anchor":"claude-in-chrome-org-policy-enforced-on-mcp-tool-refresh","heading":"Claude in Chrome tools respect the organisation's policy when refreshed","tier":"notice","area":"Claude in Chrome","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/claude-in-chrome-org-policy-enforced-on-mcp-tool-refresh","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Claude in Chrome tools respect the organisation's policy when refreshed\n\nRefreshing the Claude in Chrome server's tools, or sending it messages, now fails if the organisation's policy turns it off or cannot be read\n\n**What**\n\nClaude in Chrome connects Claude Code to your browser through an MCP server, an add-on that supplies extra tools. An organisation can turn it off with the `allow_claude_browser_extension` policy.\n\nWhen Claude Code refreshes the list of tools a server offers, it now checks that policy first:\n\n- If the policy turns Claude in Chrome off, the server's tools are not refreshed and cannot be used.\n\n- If the policy cannot be read right now, the tools are not refreshed and Claude Code asks you to try again later.\n\nMessages to the Claude in Chrome server are also stopped with an explicit error when the policy refuses it or cannot be read. Notices that cancel a request still go through.\n\n**Why**\n\nAn organisation that turns Claude in Chrome off can no longer have its tools come back through a refresh. If you see one of these errors, the organisation's policy is the reason.\n\n- Area: Claude in Chrome\n- Names: `allow_claude_browser_extension`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}