Clear mouse calibration, reverting to uncalibrated mode.
AI agents call pikvm_clear_calibration to permanently remove resources in PiKVM MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Clearing calibration data is an irreversible deletion of stored configuration. Once cleared, the previous calibration values are lost and the system reverts to an uncalibrated state, which cannot be undone without recalibrating. This fits the Destructive category as it irreversibly removes data.
From the tool's definition 'Clear mouse calibration, reverting to uncalibrated mode' — permanently removes existing calibration data and reverts state
Attacks that exploit this kind of access
Clear mouse calibration, reverting to uncalibrated mode. It is categorised as a Destructive tool in the PiKVM MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the PiKVM MCP Server MCP server in PolicyLayer and add a rule for pikvm_clear_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_clear_calibration is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the pikvm_clear_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_clear_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_clear_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 →