Click the mouse
AI agents invoke vnc_mouse_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.
Mouse clicks are UI-level actions that can trigger arbitrary operations on the remote machine (opening files, confirming dialogs, submitting forms, launching programs). The effect is execution of whatever action the click target performs, making this an Execute-category tool.
From the tool's definition 'Click the mouse' — performs a mouse click action on a remote computer via VNC, triggering UI interactions whose effects depend entirely on what is on screen at the time.
Attacks that exploit this kind of access
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_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_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_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_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_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 →