playwright_navigate · MCP Developer Server MCP

WHAT IT DOES

What playwright_navigate does on MCP Developer Server

AI agents invoke playwright_navigate 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_navigate needs a policy

This tool executes browser navigation actions whose effects depend on the URL argument provided by an AI agent. While superficially similar to a Read operation, browser navigation is Execute-category because it: (1) triggers external HTTP requests and remote code execution, (2) can interact with web applications and services, (3) effects are contingent on attacker-controlled arguments (the URL), and (4) can modify…

From the tool's definition Tool description states 'Navigate to a URL in a Playwright page' — Playwright is a browser automation framework.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

playwright_navigate Rate-limited

playwright_navigate 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_navigate": {
      "limits": [
        {
          "counter": "playwright_navigate_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_navigate

What does the playwright_navigate tool do? +

Navigate to a URL in a Playwright page. 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_navigate? +

Register the MCP Developer Server MCP server in PolicyLayer and add a rule for playwright_navigate: 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_navigate? +

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

Can I rate-limit playwright_navigate? +

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

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

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