browser.click_at_page · MCP Playwright Browser MCP

WHAT IT DOES

What browser.click_at_page does on MCP Playwright Browser

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

Clicking at arbitrary page coordinates in a browser can trigger any web action: form submissions, purchases, deletions, navigation, etc. The actual effect is entirely dependent on the page context and coordinates provided, making this an Execute-category tool with high severity since an AI agent could misuse it to perform unintended or harmful web interactions.

From the tool's definition 'Click at page coordinates (x, y). Will scroll to bring the point into view first.' — triggers a browser click action at specified coordinates, causing external side effects depending on what element is at those coordinates.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser.click_at_page Rate-limited

browser.click_at_page 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_page": {
      "limits": [
        {
          "counter": "browser.click_at_page_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_page

What does the browser.click_at_page tool do? +

Click at page coordinates (x, y). Will scroll to bring the point into view first. 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_page? +

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

browser.click_at_page 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_page? +

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

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

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