double_click
Double-click at the current position or at supplied screen coordinates.
This record as markdown: /tools/mcp-control-plane/double-click.md
What double_click does on Mcp Control Plane
AI agents invoke double_click to trigger actions in Mcp Control Plane. 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 double_click is rated High
This tool performs a GUI interaction (double-clicking) on screen coordinates, which can trigger arbitrary application actions such as opening files, launching programs, confirming dialogs, or activating UI elements. The effect is entirely dependent on what is under the cursor at the time, making it a general-purpose execution primitive with potentially wide blast radius if misused by an AI agent.
From the tool's definition Double-click at the current position or at supplied screen coordinates
Attacks that exploit this kind of access
The rule that runs double_click safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Control Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For double_click, this is the rule to start with:
double_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Control Plane, apply this rule, and every double_click call is checked against it from then on.
Questions about double_click
Double-click at the current position or at supplied screen coordinates. It is categorised as a Execute tool in the Mcp Control Plane MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for double_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 Mcp Control Plane. Nothing to install.
double_click 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 double_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.
Set action: deny in the PolicyLayer policy for double_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.
double_click is provided by the Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Control Plane, and thousands of servers like it.
Across the catalogue