playwright_evaluate · Playwright MCP Server for Security MCP

WHAT IT DOES

What playwright_evaluate does on Playwright MCP Server for Security

AI agents invoke playwright_evaluate to trigger actions in Playwright MCP Server for Security. 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_evaluate needs a policy

The tool explicitly executes JavaScript in a live browser context, which is the definition of Execute category. It can trigger any browser-based side effects (DOM manipulation, network requests, data exfiltration, XSS attacks, etc.). The lack of sandboxing or argument restrictions means an AI agent could use this to perform unauthorized actions on any website visited.

From the tool's definition 'Execute JavaScript in the browser console' - this tool runs arbitrary code with no restrictions indicated

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

playwright_evaluate Rate-limited

playwright_evaluate 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_evaluate": {
      "limits": [
        {
          "counter": "playwright_evaluate_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 Playwright MCP Server for Security, so you can run agents against it safely.

FAQ

Questions about playwright_evaluate

What does the playwright_evaluate tool do? +

Execute JavaScript in the browser console. It is categorised as a Execute tool in the Playwright MCP Server for Security 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_evaluate? +

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

What risk level is playwright_evaluate? +

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

Can I rate-limit playwright_evaluate? +

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

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

playwright_evaluate is provided by the Playwright MCP Server for Security MCP server (o0x1024/mcp-playwright-security). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.