calibrate_accelerometer · Betaflight MCP Server MCP

WHAT IT DOES

What calibrate_accelerometer does on Betaflight MCP Server

AI agents invoke calibrate_accelerometer 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_accelerometer needs a policy

Calibrating an accelerometer is an active hardware operation that modifies the stored calibration offsets on the flight controller. If performed at the wrong time or with the drone not level, it can corrupt the accelerometer calibration data, leading to incorrect attitude estimation and potentially causing crashes during flight.

From the tool's definition 'Calibrate the accelerometer' - triggers a hardware calibration routine on the flight controller requiring physical positioning ('drone must be on a level surface')

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

calibrate_accelerometer Rate-limited

calibrate_accelerometer 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_accelerometer": {
      "limits": [
        {
          "counter": "calibrate_accelerometer_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_accelerometer

What does the calibrate_accelerometer tool do? +

Calibrate the accelerometer. The drone must be on a level surface. 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_accelerometer? +

Register the Betaflight MCP Server MCP server in PolicyLayer and add a rule for calibrate_accelerometer: 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_accelerometer? +

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

Can I rate-limit calibrate_accelerometer? +

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

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

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