browser_open · AutoDev MCP: Risk & Policy

WHAT IT DOES

What browser_open does on AutoDev MCP

AI agents invoke browser_open to trigger actions in AutoDev MCP. 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_open needs a policy

This tool initiates a Playwright-based browser session, which is an external operation that triggers a browser process. It falls under Execute because it launches and controls an external browser environment, with effects depending on how the session is subsequently used. Severity is medium since opening a browser session itself has limited direct blast radius, but it enables further browser-based actions.

From the tool's definition Open browser test session (extra track, does not replace CLI tests)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_open Rate-limited

browser_open 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_open": {
      "limits": [
        {
          "counter": "browser_open_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 AutoDev MCP, so you can run agents against it safely.

FAQ

Questions about browser_open

What does the browser_open tool do? +

Open browser test session (extra track, does not replace CLI tests). It is categorised as a Execute tool in the AutoDev MCP 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_open? +

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

What risk level is browser_open? +

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

Can I rate-limit browser_open? +

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

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

browser_open is provided by the AutoDev MCP server (rookiejefren/autocoding-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

browser_open is one line of AutoDev's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →