Move the mouse cursor to a position on the remote machine. For absolute moves, coordinates are in screen pixels (0,0 = top-left). For relative moves, deltas are clamped to -127 to 127.
AI agents invoke pikvm_mouse_move to trigger actions in PiKVM 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.
This tool moves the mouse cursor on a remote physical machine, constituting a real interaction with an external system. It is an active operation that can trigger UI events, clicks, and other downstream effects depending on where the cursor moves. Given the broader server context of full physical machine control without emulation, misuse could lead to unintended interactions with critical system UI elements.
From the tool's definition Move the mouse cursor to a position on the remote machine... enables full keyboard, mouse, and screen control of a physical machine without emulation
Attacks that exploit this kind of access
Move the mouse cursor to a position on the remote machine. For absolute moves, coordinates are in screen pixels (0,0 = top-left). For relative moves, deltas are clamped to -127 to 127. It is categorised as a Execute tool in the PiKVM MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the PiKVM MCP Server MCP server in PolicyLayer and add a rule for pikvm_mouse_move: 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 PiKVM MCP Server. Nothing to install.
pikvm_mouse_move 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 pikvm_mouse_move 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 pikvm_mouse_move. 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.
pikvm_mouse_move is provided by the PiKVM MCP Server MCP server (kultivatorconsulting/pikvm_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 →