click_at · Chrome Devtools MCP: Risk & Policy

WHAT IT DOES

What click_at does on Chrome Devtools

AI agents invoke click_at to trigger actions in Chrome Devtools. 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 click_at needs a policy

Clicking in a live browser is an Execute-category action: it triggers external operations (form submissions, navigation, UI interactions, purchases, etc.) whose effects depend entirely on what is at those coordinates. The blast radius is high because a misplaced or malicious click could trigger destructive or even financial actions within the browser session.

From the tool's definition 'Clicks at the provided coordinates' — triggers a browser click action at specified coordinates in a live Chrome browser

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

click_at Rate-limited

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

FAQ

Questions about click_at

What does the click_at tool do? +

Clicks at the provided coordinates. It is categorised as a Execute tool in the Chrome Devtools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on click_at? +

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

What risk level is click_at? +

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

Can I rate-limit click_at? +

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

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

click_at is provided by the Chrome Devtools MCP server (shivamprasad99/chrome-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.