Move the pointer to (x, y) and double-click.
AI agents invoke double_click to trigger actions in ComputerMate. 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 at arbitrary screen coordinates triggers UI interactions on the controlled computer — opening files, launching applications, confirming dialogs, etc. This is an Execute-level action because its effects depend on what is present at the target coordinates and can cause wide-ranging side effects (launching programs, opening documents, activating controls).
From the tool's definition Move the pointer to (x, y) and double-click
Attacks that exploit this kind of access
Move the pointer to (x, y) and double-click. It is categorised as a Execute tool in the ComputerMate MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ComputerMate 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 ComputerMate. 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 ComputerMate MCP server (one710/computermate). 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 →