browser_close_page
Close an active browser session.
This record as markdown: /tools/2captcha-mcp-captcha-solver/browser-close-page.md
What browser_close_page does on Mcp Captcha Solver
AI agents invoke browser_close_page to trigger actions in Mcp Captcha Solver. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why browser_close_page is rated High
Closing a browser session is an external operation that terminates a running process and may discard any unsaved state or in-progress work within that session. It is not purely destructive (no data is deleted) but it executes an action with real side effects on the browser environment.
From the tool's definition Close an active browser session
Attacks that exploit this kind of access
The rule that runs browser_close_page safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Captcha Solver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_close_page, this is the rule to start with:
browser_close_page stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Captcha Solver, apply this rule, and every browser_close_page call is checked against it from then on.
Questions about browser_close_page
Close an active browser session. It is categorised as a Execute tool in the Mcp Captcha Solver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Captcha Solver MCP server in PolicyLayer and add a rule for browser_close_page: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Mcp Captcha Solver. Nothing to install.
browser_close_page is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the browser_close_page rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for browser_close_page. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
browser_close_page is provided by the Mcp Captcha Solver MCP server (2captcha/mcp-captcha-solver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Captcha Solver, and thousands of servers like it.
Across the catalogue