disconnect_from_browser

SERVERChrome Devtools SOURCEbenjaminr/chrome-devtools-mcp

Low RISK CLASS

Category Other

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/benjaminr-chrome-devtools-mcp/disconnect-from-browser.md

WHAT IT DOES

What disconnect_from_browser does on Chrome Devtools

AI agents call disconnect_from_browser as a supporting operation in Chrome Devtools workflows.

RISK

Why disconnect_from_browser is rated Low

This tool only terminates the MCP client's connection to the browser; it does not read, write, execute, delete, or move money. The browser continues running unaffected. It is a session management/cleanup operation that fits best in 'Other'. Misuse at worst causes loss of control over the browser session, which is low severity.

From the tool's definition Cleanly terminates the connection to the Chrome browser instance while leaving the browser running... The browser will continue running after disconnection

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs disconnect_from_browser safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Chrome Devtools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For disconnect_from_browser, this is the rule to start with:

disconnect_from_browser Rate-limited

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

View as policy code

policy.json

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

SET A RULE FOR THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Chrome Devtools, apply this rule, and every disconnect_from_browser call is checked against it from then on.

FAQ

Questions about disconnect_from_browser

What does the disconnect_from_browser tool do? +

Disconnect from the current browser session. Cleanly terminates the connection to the Chrome browser instance while leaving the browser running. This is useful for releasing resources or preparing to connect to a different browser instance. The browser will continue running after disconnection, but will no longer be controllable through this client until a new connection is established. Returns: Disconnection status dictionary containing: - success: Boolean indicating disconnection success - message: Human-readable status description - data: Disconnection details including: - connected: Boolean status (should be False after disconnect) Note: This function only disconnects the client from Chrome; it doesn't close or terminate the browser process itself. It is categorised as a Other tool in the Chrome Devtools MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on disconnect_from_browser? +

Register the Chrome Devtools MCP server in PolicyLayer and add a rule for disconnect_from_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 Devtools. Nothing to install.

What risk level is disconnect_from_browser? +

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

Can I rate-limit disconnect_from_browser? +

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

How do I block disconnect_from_browser completely? +

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

What MCP server provides disconnect_from_browser? +

disconnect_from_browser is provided by the Chrome Devtools MCP server (benjaminr/chrome-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Chrome Devtools, and thousands of servers like it.

This server

All 47 Chrome Devtools tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →