browser_evaluate

A execute tool on the Playwright MCP server.

SERVERPlaywright MCP SOURCEalialobidm/playwright-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/alialobidm-playwright-mcp/browser-evaluate.md

WHAT IT DOES

What browser_evaluate does on Playwright MCP

AI agents invoke browser_evaluate to trigger actions in Playwright 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.

RISK

Why browser_evaluate is rated High

In Playwright, 'evaluate' runs arbitrary JavaScript code in the browser page context. This is an Execute-category action with critical severity because it allows arbitrary code execution in the browser, enabling exfiltration of cookies/credentials, DOM manipulation, network requests, and other high-impact actions.

From the tool's definition Tool name 'browser_evaluate' in context of a Playwright browser automation MCP server strongly implies execution of arbitrary JavaScript in the browser context, which is standard Playwright API behavior (page.evaluate())

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browser_evaluate safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Playwright MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_evaluate, this is the rule to start with:

browser_evaluate Rate-limited

browser_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": {
    "browser_evaluate": {
      "limits": [
        {
          "counter": "browser_evaluate_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Playwright MCP, apply this rule, and every browser_evaluate call is checked against it from then on.

FAQ

Questions about browser_evaluate

What does the browser_evaluate tool do? +

browser_evaluate is a execute tool on the Playwright MCP server. It is categorised as a Execute tool in the Playwright 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_evaluate? +

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

What risk level is browser_evaluate? +

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

Can I rate-limit browser_evaluate? +

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

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

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

KEEP EXPLORING

More on Playwright, and thousands of servers like it.

This server

All 59 Playwright tools → High-risk tools on this server →

Across the catalogue

browser_click on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →