click_at

Clicks at the provided coordinates

SERVERChrome Devtools SOURCE@async23/chrome-devtools-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/async23-chrome-devtools-mcp/click-at.md

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.

RISK

Why click_at is rated High

Clicking at coordinates constitutes a browser action that can trigger external operations depending on what is at those coordinates (form submissions, navigation, purchases, deletions, etc.). This is an Execute-category action with medium severity because the blast radius depends heavily on context — a misused click could trigger significant unintended operations in the live browser.

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

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs click_at safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Chrome Devtools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For click_at, this is the rule to start with:

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.

The button opens the PolicyLayer dashboard: create your workspace, connect Chrome Devtools, apply this rule, and every click_at call is checked against it from then on.

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 (@async23/chrome-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Chrome Devtools, and thousands of servers like it.

This server

All 50 Chrome Devtools tools → High-risk tools on this server →

Across the catalogue

browser_click on Percepta MCP Server →qt_click on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →