Double-click at the given screen coordinates. Pass verify_app to confirm the right app is frontmost before clicking.
AI agents invoke double_click to trigger actions in Mcp Desktop. 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.
Double-clicking triggers UI actions on the desktop whose effects depend entirely on what is under the cursor — it could open files, execute programs, confirm dialogs, or activate destructive controls. Because the outcome is context-dependent and can trigger arbitrary application behavior, Execute is the appropriate category.
From the tool's definition Double-click at the given screen coordinates
Attacks that exploit this kind of access
Double-click at the given screen coordinates. Pass verify_app to confirm the right app is frontmost before clicking. It is categorised as a Execute tool in the Mcp Desktop MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Desktop 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 Desktop. 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 Desktop MCP server (mocha06/mcp-desktop). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →