chrome_click_element · Chrome MCP Server MCP: Risk & Policy

WHAT IT DOES

What chrome_click_element does on Chrome MCP Server

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

Clicking browser elements can trigger a wide range of actions: form submissions, navigation, purchases, deletions, authentication flows, etc. The actual effect is entirely argument-dependent and can be severe. This is a browser action that executes operations in an existing authenticated session, making misuse potentially high-impact.

From the tool's definition 'Click elements using CSS selectors' — clicking interactive elements in a browser (buttons, links, form submissions) triggers external operations whose effects depend on what is clicked

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

chrome_click_element Rate-limited

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

FAQ

Questions about chrome_click_element

What does the chrome_click_element tool do? +

Click elements using CSS selectors. It is categorised as a Execute tool in the Chrome MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on chrome_click_element? +

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

What risk level is chrome_click_element? +

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

Can I rate-limit chrome_click_element? +

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

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

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