Click a mouse button on the target PC, optionally at a specific position.
AI agents invoke mouse_click to trigger actions in Mcp Serial Hid Kvm. 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_click triggers a physical mouse click action on a remote PC, causing UI interactions whose effects depend entirely on where the click lands (e.g., launching programs, confirming dialogs, clicking destructive buttons). This constitutes execution of external operations with variable and potentially severe consequences, and the server description confirms full physical PC control.
From the tool's definition Click a mouse button on the target PC, optionally at a specific position
Attacks that exploit this kind of access
Click a mouse button on the target PC, optionally at a specific position. It is categorised as a Execute tool in the Mcp Serial Hid Kvm MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Serial Hid Kvm MCP server in PolicyLayer and add a rule for 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 Serial Hid Kvm. Nothing to install.
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 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 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.
mouse_click is provided by the Mcp Serial Hid Kvm MCP server (sunasaji/mcp-serial-hid-kvm). 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 →