Sequentially connect to each registered drone, backup its config,
AI agents use fleet_backup_all 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.
The tool connects to multiple registered drones and backs up their configurations. Backing up involves reading config from each drone and writing that data to storage. It is a Write operation (creating backup files/records).
From the tool's definition 'backup its config' — the tool reads configuration from each drone and writes/stores backup data sequentially across the fleet
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Sequentially connect to each registered drone, backup its config,. 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.
Register the Betaflight MCP Server MCP server in PolicyLayer and add a rule for fleet_backup_all: 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_backup_all is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the fleet_backup_all 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_backup_all. 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_backup_all 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 →