element_click · MCP Playwright Server MCP: Risk & Policy

WHAT IT DOES

What element_click does on MCP Playwright Server

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

WHY IT NEEDS A POLICY

Why element_click needs a policy

Clicking elements in a browser is an Execute-category action because the effects are entirely argument-dependent. A click could submit a payment form (Financial), delete data (Destructive), or simply navigate a page (Read). Since the worst-case outcome depends on what is clicked, Execute at high severity is appropriate — misuse could trigger irreversible or high-impact actions in a controlled browser session.

From the tool's definition 'Click an element using various locator strategies' — triggers browser click actions that can submit forms, navigate pages, trigger purchases, delete records, or activate any interactive UI element

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

element_click Rate-limited

element_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "element_click": {
      "limits": [
        {
          "counter": "element_click_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 MCP Playwright Server, so you can run agents against it safely.

FAQ

Questions about element_click

What does the element_click tool do? +

Click an element using various locator strategies. Locator types (in recommended priority order): -. It is categorised as a Execute tool in the MCP Playwright Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on element_click? +

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

What risk level is element_click? +

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

Can I rate-limit element_click? +

Yes. Add a rate_limit block to the element_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.

How do I block element_click completely? +

Set action: deny in the PolicyLayer policy for element_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.

What MCP server provides element_click? +

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