Remove a drone from the fleet registry by name
AI agents call fleet_remove_drone to permanently remove resources in Betaflight MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes drone configuration or registration data from the fleet system. While not destroying the physical drone, it removes its tracked state from the system in a way that cannot be automatically recovered. This qualifies as Destructive rather than Write (which requires reversibility).
From the tool's definition 'Remove a drone from the fleet registry by name' - the verb 'remove' combined with 'fleet registry' indicates deletion of a registry entry.
Attacks that exploit this kind of access
Remove a drone from the fleet registry by name. It is categorised as a Destructive tool in the Betaflight MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Betaflight MCP Server MCP server in PolicyLayer and add a rule for fleet_remove_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.
fleet_remove_drone is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the fleet_remove_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.
Set action: deny in the PolicyLayer policy for fleet_remove_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.
fleet_remove_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →