Get current mouse calibration state. Returns null if not calibrated.
AI agents call pikvm_get_calibration to retrieve information from PiKVM MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves the current mouse calibration state without creating, modifying, or deleting data. It has no side effects and serves purely an informational purpose. While the broader PiKVM server enables physical machine control (which could be dangerous), this specific tool only reads calibration settings. Severity is low because misuse only exposes configuration information, not sensitive data or system access.
From the tool's definition Tool name contains 'get_' and description states it 'Returns' calibration state with no modification capability. This is a query operation that retrieves existing configuration data.
Attacks that exploit this kind of access
Get current mouse calibration state. Returns null if not calibrated. It is categorised as a Read tool in the PiKVM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PiKVM MCP Server MCP server in PolicyLayer and add a rule for pikvm_get_calibration: 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_get_calibration is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the pikvm_get_calibration 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_get_calibration. 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_get_calibration 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 →