Generate a Playwright test for given scenario
AI agents use browser_generate_playwright_test to create or update resources in Playwright MCP with Electron Support — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Playwright MCP with Electron Support environment.
This tool creates a Playwright test script based on a described scenario. It generates/writes code or a test file, which is a Write operation (creating new content). It does not execute the test, delete data, or involve financial transactions. However, the generated test could later be executed to perform browser automation, so there's some indirect risk.
From the tool's definition Generate a Playwright test for given scenario
Documented attack patterns abuse exactly the kind of access browser_generate_playwright_test gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Playwright MCP with Electron Support, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_generate_playwright_test:
{
"version": "1",
"default": "deny",
"tools": {
"browser_generate_playwright_test": {
"limits": [
{
"counter": "browser_generate_playwright_test_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}browser_generate_playwright_test stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Generate a Playwright test for given scenario. It is categorised as a Write tool in the Playwright MCP with Electron Support MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Playwright MCP with Electron Support 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 with Electron Support. Nothing to install.
browser_generate_playwright_test is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
browser_generate_playwright_test is provided by the Playwright MCP with Electron Support MCP server (robertn702/playwright-mcp-electron). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Playwright MCP with Electron Support, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
34 Playwright MCP with Electron Support tools catalogued and risk-classified — across an index of 43,000+ MCP servers.