Start mouse coordinate calibration. Moves cursor to screen center and returns expected position. Take a screenshot after calling this to visually verify actual cursor position, then call pikvm_set_calibration with calculated factors.
AI agents invoke pikvm_calibrate 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 executes an operation that causes observable effects on a connected physical machine by moving the mouse cursor. While it does not delete data (Destructive), modify persistent data (Write), or move money (Financial), it performs an active control action similar to 'click' or 'move' operations that alter the state of an external system.
From the tool's definition The tool 'pikvm_calibrate' initiates mouse coordinate calibration by moving the cursor to the screen center and returning expected position.
Attacks that exploit this kind of access
Start mouse coordinate calibration. Moves cursor to screen center and returns expected position. Take a screenshot after calling this to visually verify actual cursor position, then call pikvm_set_calibration with calculated factors. 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_calibrate: 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_calibrate 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_calibrate 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_calibrate. 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_calibrate 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 →