{"version":"2.1.310","anchor":"remote-browser-tool-calls-refused-outside-permission-checks","canonical_anchor":"remote-browser-tool-calls-refused-outside-permission-checks","heading":"Cloud browser tools can only be called by the model, through a permission check","tier":"notice","area":"Cloud Browser","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/remote-browser-tool-calls-refused-outside-permission-checks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Cloud browser tools can only be called by the model, through a permission check\n\nCalls to the 'remote-browser' cloud browser MCP server that would skip auto mode's safety check or a person's approval are now refused\n\n**What**\n\nThe cloud browser is a web browser that runs in the cloud. It reaches Claude Code through an MCP server named `remote-browser`, an outside program that gives Claude Code extra tools. Calls to it must now go through its permission check.\n\n- A new guard on MCP `tools\/call` requests rejects a call to the cloud browser tool when `refusesRemoteBrowserCallOutsideChecks` finds it is outside its permission check. The error is `REMOTE_BROWSER_OUTSIDE_CHECKS_REFUSED`, with the message \"cloud browser called outside its permission check\". Before, such a request went straight through.\n\n- A new refusal message explains the rule: \"Tools of MCP server 'remote-browser' (the cloud browser) can only be called by the model in this session, where each call gets auto mode's safety check or a person's approval; this call would skip both.\"\n\n**Why**\n\nEvery cloud browser action now gets either auto mode's safety check or your approval. Anything that tries to call the cloud browser another way is refused with one of these messages.\n\n- Area: Cloud Browser\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}