browser_screen_click · Playwright MCP: Risk & Policy

WHAT IT DOES

What browser_screen_click does on Playwright MCP

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

Clicking a mouse button in a browser context is an Execute-level action: it drives external browser state and can trigger arbitrary web operations (form submissions, purchases, deletions, navigation) depending on where the click lands. The blast radius is high because an agent could misuse this to interact with sensitive or destructive UI controls.

From the tool's definition 'Click left mouse button' — triggers a browser interaction that can activate UI elements, submit forms, follow links, or initiate any web action depending on arguments.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_screen_click Rate-limited

browser_screen_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_screen_click": {
      "limits": [
        {
          "counter": "browser_screen_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 Playwright MCP, so you can run agents against it safely.

FAQ

Questions about browser_screen_click

What does the browser_screen_click tool do? +

Click left mouse button. It is categorised as a Execute tool in the Playwright MCP 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_screen_click? +

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

What risk level is browser_screen_click? +

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

Can I rate-limit browser_screen_click? +

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

Set action: deny in the PolicyLayer policy for browser_screen_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_screen_click? +

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