browser_start · Daytona Playwright MCP Server MCP

WHAT IT DOES

What browser_start does on Daytona Playwright MCP Server

AI agents invoke browser_start to trigger actions in Daytona Playwright MCP 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 browser_start needs a policy

Starting a browser session is an Execute action because it launches an external process/operation in a cloud sandbox whose side effects are determined by what the agent does with it afterward.

From the tool's definition Tool description states it 'Start[s] a new browser session in a Daytona sandbox' — this initiates a controlled but external operation (browser automation in a cloud environment) whose effects depend on subsequent interactions.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_start Rate-limited

browser_start 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_start": {
      "limits": [
        {
          "counter": "browser_start_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 Daytona Playwright MCP Server, so you can run agents against it safely.

FAQ

Questions about browser_start

What does the browser_start tool do? +

Start a new browser session in a Daytona sandbox. It is categorised as a Execute tool in the Daytona Playwright MCP 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 browser_start? +

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

What risk level is browser_start? +

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

Can I rate-limit browser_start? +

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

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

browser_start is provided by the Daytona Playwright MCP Server MCP server (jamesmurdza/playwright-daytona-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.