Click an interactive element by its index in the page. Indices are returned by getPageInfo. Always check the page info after clicking. For text input fields, prefer using focusElementByIndex instead.
AI agents invoke clickElementByIndex 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.
Clicking interactive elements in a browser triggers external operations whose effects depend on what element is clicked — could submit forms, trigger purchases, navigate pages, activate controls, etc. The actual effect is argument-dependent and could span a wide range of consequences, making Execute the appropriate category with high severity due to potential for significant unintended actions.
From the tool's definition Click an interactive element by its index in the page... Always check the page info after clicking.
Documented attack patterns abuse exactly the kind of access clickElementByIndex gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Chrome MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for clickElementByIndex:
{
"version": "1",
"default": "deny",
"tools": {
"clickElementByIndex": {
"limits": [
{
"counter": "clickelementbyindex_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}clickElementByIndex 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.
Free to start. No card required.
Click an interactive element by its index in the page. Indices are returned by getPageInfo. Always check the page info after clicking. For text input fields, prefer using focusElementByIndex instead. 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.
Register the Chrome MCP Server MCP server in PolicyLayer and add a rule for clickElementByIndex: 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.
clickElementByIndex is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the clickElementByIndex 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.
Set action: deny in the PolicyLayer policy for clickElementByIndex. 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.
clickElementByIndex is provided by the Chrome MCP Server MCP server (lxe/chrome-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Chrome MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
11 Chrome MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.