browser_disconnect

THE RISK

Low Risk

Why browser_disconnect needs a policy

This tool terminates a debugging protocol connection but explicitly does not kill the Chrome process or modify any data. It is a teardown/cleanup operation with no read, write, execute, destructive, or financial impact. The closest category is Other since it neither retrieves data nor modifies any persistent state.

From the tool's definition Close the CDP connection to Chrome. Does NOT kill the Chrome process.

Documented attack patterns abuse exactly the kind of access browser_disconnect gives an agent:

POLICY

How to control browser_disconnect

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Accessibility Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_disconnect:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_disconnect": {
      "limits": [
        {
          "counter": "browser_disconnect_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

browser_disconnect gets a rate cap, and everything else on the server is denied unless you say otherwise.

Create a free account and register MCP Accessibility Bridge — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

SET A RULE FOR THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP Accessibility Bridge tools

Execute browser_navigate Navigate the connected browser to a URL. Execute browser_connect Connect to a running Chrome browser via the Chrome DevTools Protocol (CDP). Read get_accessibility_tree Capture a snapshot of the current page\ Read get_element_properties Given a CSS selector, returns the element\ Read get_focused_element Returns the currently keyboard-focused element\ Read get_interactive_elements Find all interactive elements on the page (buttons, inputs, links, etc.) Read query_accessibility_tree Search the accessibility tree by ARIA role and/or accessible name.

All 8 MCP Accessibility Bridge tools →

Other tools on other servers

Android Forensics ADB MCP Server generate_app_analysis_report Ethereum Tools add Math MCP Server complex_analysis_suite Crypto_MCP aes_encrypt

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Tool risk categories → How PolicyLayer classifies MCP tools by what they can do.
MCP tool → What an MCP tool is and how clients discover and call it.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about browser_disconnect

What does the browser_disconnect tool do? +

Close the CDP connection to Chrome. Does NOT kill the Chrome process. It is categorised as a Other tool in the MCP Accessibility Bridge MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on browser_disconnect? +

Register the MCP Accessibility Bridge MCP server in PolicyLayer and add a rule for browser_disconnect: 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 Accessibility Bridge. Nothing to install.

What risk level is browser_disconnect? +

browser_disconnect is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit browser_disconnect? +

Yes. Add a rate_limit block to the browser_disconnect 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.

How do I block browser_disconnect completely? +

Set action: deny in the PolicyLayer policy for browser_disconnect. 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.

What MCP server provides browser_disconnect? +

browser_disconnect is provided by the MCP Accessibility Bridge MCP server (yashpreetbathla/mcp-accessibility-bridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Accessibility Bridge tool call.

Start from MCP Accessibility Bridge, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →