browser_stop_record_network · Byob MCP: Risk & Policy

WHAT IT DOES

What browser_stop_record_network does on Byob

AI agents invoke browser_stop_record_network 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_stop_record_network needs a policy

This tool stops an ongoing network recording operation in a real Chrome browser. It triggers an external browser operation (halting a recording process), which classifies it as Execute. The severity is medium because stopping a network recording could affect monitoring/auditing capabilities, though it has limited direct destructive impact on its own.

From the tool's definition 'Stop a recording previously started with browser_start_record_network' — terminates an active network recording session in the browser

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_stop_record_network Rate-limited

browser_stop_record_network 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_stop_record_network": {
      "limits": [
        {
          "counter": "browser_stop_record_network_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_stop_record_network

What does the browser_stop_record_network tool do? +

Stop a recording previously started with browser_start_record_network and. 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_stop_record_network? +

Register the Byob MCP server in PolicyLayer and add a rule for browser_stop_record_network: 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_stop_record_network? +

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

Can I rate-limit browser_stop_record_network? +

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

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

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