browser_generate_playwright_test

WHAT IT DOES

What browser_generate_playwright_test does on Playwright MCP

AI agents invoke browser_generate_playwright_test 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.

WHY IT NEEDS A POLICY

Why browser_generate_playwright_test needs a policy

This tool generates Playwright test code for a given scenario. Generating test scripts is an Execute-category action because it produces runnable code that can interact with web pages, trigger external operations, and perform browser automation. If the generated tests are executed, they could have wide-ranging effects depending on the scenario.

From the tool's definition 'Generate a Playwright test for given scenario' — generates and likely executes browser automation test code

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_generate_playwright_test Rate-limited

browser_generate_playwright_test 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_generate_playwright_test": {
      "limits": [
        {
          "counter": "browser_generate_playwright_test_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, so you can run agents against it safely.

FAQ

Questions about browser_generate_playwright_test

What does the browser_generate_playwright_test tool do? +

Generate a Playwright test for given scenario. 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_generate_playwright_test? +

Register the Playwright MCP server in PolicyLayer and add a rule for browser_generate_playwright_test: 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_generate_playwright_test? +

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

Can I rate-limit browser_generate_playwright_test? +

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

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

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