browser_open_session · MCP: Risk & Policy

WHAT IT DOES

What browser_open_session does on Mcp

AI agents invoke browser_open_session to trigger actions in 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_session needs a policy

This tool launches a real browser process (Playwright Chromium), which is an external execution environment. It creates a persistent, stateful session that can be used to interact with web content, execute JavaScript, and perform browser actions. The execution of a browser engine and the stateful session it creates go beyond a simple read or write operation, placing it firmly in the Execute category.

From the tool's definition Create a stateful browser session backed by Playwright Chromium

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_open_session Rate-limited

browser_open_session 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_session": {
      "limits": [
        {
          "counter": "browser_open_session_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 Mcp, so you can run agents against it safely.

FAQ

Questions about browser_open_session

What does the browser_open_session tool do? +

Create a stateful browser session backed by Playwright Chromium. It is categorised as a Execute tool in the 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_session? +

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

What risk level is browser_open_session? +

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

Can I rate-limit browser_open_session? +

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

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

browser_open_session is provided by the MCP server (victormyschik/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.