pikvm_auto_calibrate · PiKVM MCP Server MCP: Risk & Policy

WHAT IT DOES

What pikvm_auto_calibrate does on PiKVM MCP Server

AI agents invoke pikvm_auto_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.

WHY IT NEEDS A POLICY

Why pikvm_auto_calibrate needs a policy

This tool actively moves the mouse on a physical machine and captures screenshots to compute calibration factors. It triggers external operations (mouse movements and screen captures) on real hardware, making it Execute category. The severity is medium because it temporarily blocks other tools and interacts with physical hardware, though its primary purpose is calibration rather than destructive or financial action.

From the tool's definition Moves the mouse multiple times, compares screenshots to find the cursor, and computes calibration factors. Other tools are blocked during calibration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pikvm_auto_calibrate Rate-limited

pikvm_auto_calibrate stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pikvm_auto_calibrate": {
      "limits": [
        {
          "counter": "pikvm_auto_calibrate_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches PiKVM MCP Server, so you can run agents against it safely.

FAQ

Questions about pikvm_auto_calibrate

What does the pikvm_auto_calibrate tool do? +

Automatically calibrate mouse coordinates by detecting the cursor position via screenshot diffing. This is more accurate than manual calibration. Moves the mouse multiple times, compares screenshots to find the cursor, and computes calibration factors. Other tools are blocked during calibration. 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.

How do I enforce a policy on pikvm_auto_calibrate? +

Register the PiKVM MCP Server MCP server in PolicyLayer and add a rule for pikvm_auto_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.

What risk level is pikvm_auto_calibrate? +

pikvm_auto_calibrate is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit pikvm_auto_calibrate? +

Yes. Add a rate_limit block to the pikvm_auto_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.

How do I block pikvm_auto_calibrate completely? +

Set action: deny in the PolicyLayer policy for pikvm_auto_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.

What MCP server provides pikvm_auto_calibrate? +

pikvm_auto_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.