browser_intercept_stop · Byob MCP: Risk & Policy

WHAT IT DOES

What browser_intercept_stop does on Byob

AI agents invoke browser_intercept_stop to trigger actions in Byob. 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 browser_intercept_stop needs a policy

Stopping an interceptor affects browser behavior and network operations in ways that depend on context and prior state. While not directly destructive or financial, it executes control logic over browser internals. The incomplete description ('Stop a') limits confidence, but the sibling tools (browser_eval, browser_click, browser_drag) confirm this server provides Execute-level capabilities.

From the tool's definition Tool is part of byob server which 'control[s] your real Chrome browser' and performs 'web tasks'; 'browser_intercept_stop' implies control of browser request/response interception—a mechanism for modifying network behavior.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_intercept_stop Rate-limited

browser_intercept_stop 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": {
    "browser_intercept_stop": {
      "limits": [
        {
          "counter": "browser_intercept_stop_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 Byob, so you can run agents against it safely.

FAQ

Questions about browser_intercept_stop

What does the browser_intercept_stop tool do? +

Stop a. It is categorised as a Execute tool in the Byob MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on browser_intercept_stop? +

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

What risk level is browser_intercept_stop? +

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

Can I rate-limit browser_intercept_stop? +

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

Set action: deny in the PolicyLayer policy for browser_intercept_stop. 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_intercept_stop? +

browser_intercept_stop is provided by the Byob MCP server (wxtsky/byob). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.