pikvm_set_calibration · PiKVM MCP Server MCP: Risk & Policy

WHAT IT DOES

What pikvm_set_calibration does on PiKVM MCP Server

AI agents use pikvm_set_calibration to create or update resources in PiKVM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PiKVM MCP Server environment.

WHY IT NEEDS A POLICY

Why pikvm_set_calibration needs a policy

This tool writes/updates calibration configuration data (coordinate scaling factors) for mouse input. It modifies stored settings reversibly and does not execute commands, delete data, or have financial implications. The blast radius is low as miscalibration would only affect mouse movement accuracy, which can be corrected by recalibrating.

From the tool's definition Set mouse coordinate calibration factors. Calculate factors as: factorX = expected_x / actual_x, factorY = expected_y / actual_y.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pikvm_set_calibration Rate-limited

pikvm_set_calibration stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_set_calibration": {
      "limits": [
        {
          "counter": "pikvm_set_calibration_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_set_calibration

What does the pikvm_set_calibration tool do? +

Set mouse coordinate calibration factors. Calculate factors as: factorX = expected_x / actual_x, factorY = expected_y / actual_y. For example, if calibration moved cursor to expected (960, 540) but it landed at (720, 405), factors would be 960/720=1.33 and 540/405=1.33. It is categorised as a Write tool in the PiKVM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on pikvm_set_calibration? +

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

What risk level is pikvm_set_calibration? +

pikvm_set_calibration is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit pikvm_set_calibration? +

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

How do I block pikvm_set_calibration completely? +

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

What MCP server provides pikvm_set_calibration? +

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