{"version":"2.1.260","anchor":"browser-extension-access-now-also-gated-in-a-general-permiss","canonical_anchor":"browser-extension-access-now-also-gated-in-a-general-permiss","heading":"Browser-extension access now also gated in a general permission-scope check","tier":"notice","area":"Chrome & Browser","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/browser-extension-access-now-also-gated-in-a-general-permiss","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Browser-extension access now also gated in a general permission-scope check\n\nBrowser-extension access is now also checked by the general MCP\/tool permission-scope gate.\n\nBrowser-extension connections are now denied by the generic MCP\/tool scope-permission check (`Ah`) when they don't come from the SDK, independent of the existing scope allowlist. This closes off a path that previously wasn't checked against the `allow_claude_browser_extension` gate.\n\n- Area: Chrome & Browser\n- Names: `allow_claude_browser_extension`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}