Double click at specific x,y coordinates in the browser window. Useful for text selection or other double-click specific actions. Always check the page info after double clicking.
AI agents invoke doubleClick 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.
This tool triggers browser interactions (double-click) at arbitrary coordinates, which can activate UI elements, open files, submit forms, or trigger application-specific behaviors depending on what's on the page. As part of a browser automation suite that controls Chrome, misuse could activate unintended actions across any web application the browser is navigating.
From the tool's definition Double click at specific x,y coordinates in the browser window... Useful for text selection or other double-click specific actions.
Documented attack patterns abuse exactly the kind of access doubleClick 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 doubleClick:
{
"version": "1",
"default": "deny",
"tools": {
"doubleClick": {
"limits": [
{
"counter": "doubleclick_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} doubleClick 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.
Double click at specific x,y coordinates in the browser window. Useful for text selection or other double-click specific actions. Always check the page info after double clicking. 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 doubleClick: 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.
doubleClick 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 doubleClick 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 doubleClick. 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.
doubleClick 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.