calibrate_magnetometer · Betaflight MCP Server MCP

WHAT IT DOES

What calibrate_magnetometer does on Betaflight MCP Server

AI agents invoke calibrate_magnetometer to trigger actions in Betaflight 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 calibrate_magnetometer needs a policy

This is an Execute tool because it triggers an external operation (magnetometer calibration sequence) whose effects depend on runtime conditions and user actions (drone rotation). While not destructive or financially harmful, it performs an active operation that changes drone sensor configuration state and could affect flight behavior if performed incorrectly.

From the tool's definition Tool name 'calibrate_magnetometer' and description 'Start magnetometer (compass) calibration. Rotate the drone through' indicate the tool initiates a hardware calibration routine that requires physical drone movement and alters sensor state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

calibrate_magnetometer Rate-limited

calibrate_magnetometer 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": {
    "calibrate_magnetometer": {
      "limits": [
        {
          "counter": "calibrate_magnetometer_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 Betaflight MCP Server, so you can run agents against it safely.

FAQ

Questions about calibrate_magnetometer

What does the calibrate_magnetometer tool do? +

Start magnetometer (compass) calibration. Rotate the drone through. It is categorised as a Execute tool in the Betaflight 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 calibrate_magnetometer? +

Register the Betaflight MCP Server MCP server in PolicyLayer and add a rule for calibrate_magnetometer: 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 Betaflight MCP Server. Nothing to install.

What risk level is calibrate_magnetometer? +

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

Can I rate-limit calibrate_magnetometer? +

Yes. Add a rate_limit block to the calibrate_magnetometer 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 calibrate_magnetometer completely? +

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

calibrate_magnetometer is provided by the Betaflight MCP Server MCP server (jir13/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.