stop_motors · Betaflight MCP Server MCP: Risk & Policy

WHAT IT DOES

What stop_motors does on Betaflight MCP Server

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

This tool executes an external operation (stopping drone motors) whose effects are immediate and depend on system state. While not destructive in the data sense, it triggers a real-world physical action that could cause loss of vehicle control, crashes, injury, or property damage if invoked without appropriate context. The critical severity reflects the high-risk nature of motor control commands in aviation contexts.

From the tool's definition Tool name 'stop_motors' and description 'Stop all motors immediately' indicate direct execution of a physical control action on drone hardware with immediate effect.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_motors Rate-limited

stop_motors 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": {
    "stop_motors": {
      "limits": [
        {
          "counter": "stop_motors_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 stop_motors

What does the stop_motors tool do? +

Stop all motors immediately. 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 stop_motors? +

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

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

Can I rate-limit stop_motors? +

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

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

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