test_motor · Betaflight MCP Server MCP: Risk & Policy

WHAT IT DOES

What test_motor does on Betaflight MCP Server

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

This tool physically activates a motor on a drone flight controller. While it is an execution of an external hardware operation rather than a data deletion, it poses extreme physical danger — spinning a motor with propellers attached can cause severe injury.

From the tool's definition DANGER: Spin a single motor for testing. REMOVE PROPS FIRST!

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

test_motor Rate-limited

test_motor 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": {
    "test_motor": {
      "limits": [
        {
          "counter": "test_motor_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 test_motor

What does the test_motor tool do? +

DANGER: Spin a single motor for testing. REMOVE PROPS FIRST!. 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 test_motor? +

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

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

Can I rate-limit test_motor? +

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

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

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

// THE FULL RECORD

test_motor is one line of Betaflight MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →