playwright_launch_browser · MCP Developer Server MCP

WHAT IT DOES

What playwright_launch_browser does on MCP Developer Server

AI agents invoke playwright_launch_browser to trigger actions in MCP Developer Server. 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 playwright_launch_browser needs a policy

Launching a browser is an Execute operation: it triggers external processes and runtime behavior whose effects depend on subsequent browser automation arguments (navigation, interaction, script injection). While not immediately destructive, browser instances can perform arbitrary web interactions, access external URLs, and potentially expose sensitive data or perform unauthorized actions.

From the tool's definition Tool 'playwright_launch_browser' launches a browser instance which executes external operations (browser automation).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

playwright_launch_browser Rate-limited

playwright_launch_browser 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": {
    "playwright_launch_browser": {
      "limits": [
        {
          "counter": "playwright_launch_browser_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 Developer Server, so you can run agents against it safely.

FAQ

Questions about playwright_launch_browser

What does the playwright_launch_browser tool do? +

Launch a new Playwright browser instance (chromium, firefox, or webkit). Supports headless, so try to use Headless. It is categorised as a Execute tool in the MCP Developer Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on playwright_launch_browser? +

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

What risk level is playwright_launch_browser? +

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

Can I rate-limit playwright_launch_browser? +

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

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

playwright_launch_browser is provided by the MCP Developer Server MCP server (ra86-dev/mcpdockershell). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.