browser_disconnect

THE RISK

Low Risk

Why browser_disconnect needs a policy

This tool terminates a debugging connection to a browser tab. It does not read, write, execute code, delete data, or involve financial operations. It simply closes a monitoring/inspection session, which is a connection management operation. No data is created, modified, or destroyed as a result.

From the tool's definition Disconnect from a specific browser tab

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 Browser Connect, 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 Browser Connect — 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 Browser Connect tools

Execute browser_launch Launch a new browser instance with debugging enabled Execute performance_profile Advanced performance profiling with bottleneck detection and recommendations Execute debug_localhost Launch browser with a localhost URL and automatically connect for debugging Execute backend_debugger_attach Attach to a Node.js process debugger for breakpoint debugging Execute browser_connect Connect to a specific browser tab for debugging Read network_performance Get network performance statistics for a connected browser tab Read backend_logs_stream Stream and search logs from backend applications (files, processes, Docker containers) Read browser_list_tabs List all available browser tabs that can be connected to

All 16 Browser Connect 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? +

Disconnect from a specific browser tab. It is categorised as a Other tool in the Browser Connect MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on browser_disconnect? +

Register the Browser Connect 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 Browser Connect. 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 Browser Connect MCP server (perception30/browser-connect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Browser Connect tool call.

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

CHECK YOUR STACK →