Restaurar un modelo desde un backup.
AI agents use restore_model 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.
Restoring from a backup is a Write operation—it modifies the drone's configuration state reversibly (can be backed up and restored again). It's not Destructive because the operation is reversible and doesn't permanently delete data. It's not Execute because it doesn't run arbitrary code or trigger unpredictable side effects; it applies a known saved state.
From the tool's definition Tool name 'restore_model' with description 'Restaurar un modelo desde un backup' (Restore a model from a backup) indicates loading/applying saved configuration state to a drone flight controller.
Attacks that exploit this kind of access
Restaurar un modelo desde un backup. 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 restore_model: 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.
restore_model 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 restore_model 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 restore_model. 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.
restore_model 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 →