chrome_click · Chrome MCP Stealth MCP: Risk & Policy

WHAT IT DOES

What chrome_click does on Chrome MCP Stealth

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

Clicking elements in a browser can trigger arbitrary external operations — submitting forms, initiating purchases, navigating to new pages, or activating destructive UI actions. The stealth capability (bypassing bot detection) amplifies risk.

From the tool's definition 'Click an element. Stealth: Bezier mouse + jitter. Fast: instant.' — triggers browser interaction/UI actions that can cause navigation, form submissions, purchases, or other irreversible side effects depending on target element

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

chrome_click Rate-limited

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

FAQ

Questions about chrome_click

What does the chrome_click tool do? +

Click an element. Stealth: Bezier mouse + jitter. Fast: instant. Examples:. It is categorised as a Execute tool in the Chrome MCP Stealth 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? +

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

What risk level is chrome_click? +

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

Can I rate-limit chrome_click? +

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

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

chrome_click is provided by the Chrome MCP Stealth MCP server (riaan-fourie/chrome-mcp-stealth). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.