web_disconnect · Web Bridge MCP: Risk & Policy

WHAT IT DOES

What web_disconnect does on Web Bridge

AI agents invoke web_disconnect to trigger actions in Web Bridge. 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 IT NEEDS A POLICY

Why web_disconnect needs a policy

This tool terminates an active browser session and releases associated resources. It triggers an external operation (disconnecting from a browser/page) that affects the runtime environment. While not destructive to persistent data, it irreversibly ends the current session state (unsaved form data, session context, etc.) and could disrupt ongoing automation workflows.

From the tool's definition 'Disconnect from current web page and release browser resources'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

web_disconnect Rate-limited

web_disconnect 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "web_disconnect": {
      "limits": [
        {
          "counter": "web_disconnect_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Web Bridge, so you can run agents against it safely.

FAQ

Questions about web_disconnect

What does the web_disconnect tool do? +

Disconnect from current web page and release browser resources. It is categorised as a Execute tool in the Web Bridge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on web_disconnect? +

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

What risk level is web_disconnect? +

web_disconnect is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit web_disconnect? +

Yes. Add a rate_limit block to the web_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 web_disconnect completely? +

Set action: deny in the PolicyLayer policy for web_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 web_disconnect? +

web_disconnect is provided by the Web Bridge MCP server (@midscene/web-bridge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.