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

WHAT IT DOES

What browser.click_at does on MCP Playwright Browser

AI agents invoke browser.click_at 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_at needs a policy

Clicking at specific coordinates triggers UI interactions that can cause arbitrary side effects depending on what element is at those coordinates — submitting forms, triggering purchases, deleting content, navigating pages, etc. The effect is entirely argument-dependent, making this an Execute-class tool with high blast radius since an AI agent could click on destructive or financial UI elements.

From the tool's definition Click at viewport coordinates (x, y)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser.click_at Rate-limited

browser.click_at 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_at": {
      "limits": [
        {
          "counter": "browser.click_at_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_at

What does the browser.click_at tool do? +

Click at viewport coordinates (x, y). Use browser.click_at_page for page coordinates. 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_at? +

Register the MCP Playwright Browser MCP server in PolicyLayer and add a rule for browser.click_at: 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_at? +

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

Can I rate-limit browser.click_at? +

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

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

browser.click_at 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.