Double click the mouse
AI agents invoke vnc_mouse_double_click to trigger actions in VNC 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.
A double-click is a user interaction that executes actions in a GUI environment (opening files, launching apps, activating controls). Combined with the server's stated purpose of 'control computers via VNC', this constitutes remote execution of arbitrary UI actions. Effects depend entirely on what is under the cursor at the time, potentially triggering destructive or financial operations.
From the tool's definition Double click the mouse — triggers UI actions on a remote computer via VNC, such as opening files, launching applications, or confirming dialogs
Attacks that exploit this kind of access
Double click the mouse. It is categorised as a Execute tool in the VNC MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the VNC MCP Server MCP server in PolicyLayer and add a rule for vnc_mouse_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 VNC MCP Server. Nothing to install.
vnc_mouse_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 vnc_mouse_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 vnc_mouse_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.
vnc_mouse_double_click is provided by the VNC MCP Server MCP server (volkan-m/vnc-mcp-server). 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 →