AI agents invoke playwright_click to trigger actions in Playwright MCP 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.
Clicking is a browser action that executes external operations with context-dependent effects. A click could be benign (navigation) or high-impact (form submission, financial transaction, data deletion). Classified as Execute since the action itself is an interaction trigger; the blast radius is medium because the actual impact depends entirely on the target element.
From the tool's definition 'Click an element on the page' — triggers browser interactions whose effects depend on what element is clicked (could submit forms, trigger purchases, delete items, navigate pages, etc.)
Documented attack patterns abuse exactly the kind of access playwright_click gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Playwright MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for playwright_click:
{
"version": "1",
"default": "deny",
"tools": {
"playwright_click": {
"limits": [
{
"counter": "playwright_click_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}playwright_click 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.
Free to start. No card required.
Click an element on the page. It is categorised as a Execute tool in the Playwright MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Playwright MCP Server MCP server in PolicyLayer and add a rule for playwright_click: 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. Nothing to install.
playwright_click is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the playwright_click 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 playwright_click. 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.
playwright_click is provided by the Playwright MCP Server MCP server (pvinis/mcp-playwright-stealth). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Playwright MCP Server, 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.
29 Playwright MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.