AI agents call close_browser to permanently remove resources in Chrome Debug MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Closing a browser connection is irreversible in the moment: any unsaved state, open sessions, or in-progress operations are lost. It cannot be undone (the browser session is gone). This is more severe than a simple write, placing it in Destructive. Severity is medium because it affects only the browser session rather than persistent data storage.
From the tool's definition close_browser / 关闭浏览器连接 — terminates/closes the browser connection
Documented attack patterns abuse exactly the kind of access close_browser gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Chrome Debug MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for close_browser:
{
"version": "1",
"default": "deny",
"hide": [
"close_browser"
]
}close_browser disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
关闭浏览器连接. It is categorised as a Destructive tool in the Chrome Debug MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Chrome Debug MCP Server MCP server in PolicyLayer and add a rule for close_browser: 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 Chrome Debug MCP Server. Nothing to install.
close_browser is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the close_browser 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 close_browser. 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.
close_browser is provided by the Chrome Debug MCP Server MCP server (rainmen-xia/chrome-debug-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Chrome Debug MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 Chrome Debug MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.