browser.click · MCP Playwright Browser MCP: Risk & Policy

WHAT IT DOES

What browser.click does on MCP Playwright Browser

AI agents invoke browser.click to trigger actions in MCP Playwright Browser. 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.click needs a policy

Clicking elements in a browser is an Execute-category action because its effects depend entirely on what element is clicked. A misused agent could click payment buttons, delete confirmations, form submissions, or authentication actions. The server description notes stealth mode to bypass bot detection, further elevating risk.

From the tool's definition Click an element by elementId, selector, or text — triggers browser interactions that can submit forms, navigate pages, initiate purchases, or cause other external operations

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser.click Rate-limited

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

FAQ

Questions about browser.click

What does the browser.click tool do? +

Click an element by elementId, selector, or text. It is categorised as a Execute tool in the MCP Playwright Browser 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.click? +

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

What risk level is browser.click? +

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

Can I rate-limit browser.click? +

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

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

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