fleet_register_drone · Betaflight MCP Server MCP

WHAT IT DOES

What fleet_register_drone does on Betaflight MCP Server

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

WHY IT NEEDS A POLICY

Why fleet_register_drone needs a policy

This tool creates/writes a new drone entry to a fleet registry with descriptive metadata (name, port, board info, notes). It is reversible (the entry can be updated or removed later) and has no destructive or execute effects. The action is a standard create/record operation on local fleet data, not a physical drone command. While part of a drone control system, registration is purely data management.

From the tool's definition Tool name 'fleet_register_drone' and description 'Register a drone in the fleet registry with name, port, board info, and notes' indicate the tool creates or records new drone metadata in a registry database without deleting or executing commands on hardware.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

fleet_register_drone Rate-limited

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

FAQ

Questions about fleet_register_drone

What does the fleet_register_drone tool do? +

Register a drone in the fleet registry with name, port, board info, and notes. It is categorised as a Write tool in the Betaflight 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 fleet_register_drone? +

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

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

Can I rate-limit fleet_register_drone? +

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

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

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