Click at screen coordinates using the mouse
AI agents invoke desktop_mouse_click to trigger actions in MCP Desktop Tools. 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.
This tool performs native mouse click actions at arbitrary screen coordinates, enabling interaction with any UI element on the desktop. An AI agent could misuse this to click confirmation dialogs, authorize transactions, dismiss warnings, or interact with sensitive system controls.
From the tool's definition Click at screen coordinates using the mouse
Attacks that exploit this kind of access
Click at screen coordinates using the mouse. It is categorised as a Execute tool in the MCP Desktop Tools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Desktop Tools MCP server in PolicyLayer and add a rule for desktop_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 MCP Desktop Tools. Nothing to install.
desktop_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 desktop_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 desktop_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.
desktop_mouse_click is provided by the MCP Desktop Tools MCP server (k1ta141k/mcp-desktop-tools). 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 →