click

Clicks on the provided element

SERVERChrome DevTools MCP SOURCEanirbandz/chrome_mcp_devtool

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/anirbandz-chrome-mcp-devtool/click.md

WHAT IT DOES

What click does on Chrome DevTools MCP

AI agents invoke click to trigger actions in Chrome DevTools 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.

RISK

Why click is rated High

Clicking a UI element is an external browser action whose effects are entirely argument-dependent. It could submit forms, trigger purchases, navigate pages, or invoke any browser-side behavior. This is a classic Execute-category action. Severity is medium because misuse could trigger unintended operations, but the blast radius depends heavily on context.

From the tool's definition 'Clicks on the provided element' — triggers a browser click action via Chrome DevTools Protocol, causing external side effects depending on what element is clicked (form submissions, navigation, UI interactions).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs click safely

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

click Rate-limited

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": {
    "click": {
      "limits": [
        {
          "counter": "click_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 MCP, apply this rule, and every click call is checked against it from then on.

FAQ

Questions about click

What does the click tool do? +

Clicks on the provided element. It is categorised as a Execute tool in the Chrome DevTools 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 click? +

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

What risk level is click? +

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

Can I rate-limit click? +

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

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

click is provided by the Chrome DevTools MCP server (anirbandz/chrome_mcp_devtool). 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 26 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 →