Save current settings to EEPROM. Call this after making changes
AI agents use save_settings 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.
This tool writes configuration data to EEPROM (persistent storage), making changes permanent and irreversible until overwritten. While not destructive in the sense of data deletion, it commits state changes to hardware. Given the drone control context, misconfigured settings could impact flight safety.
From the tool's definition Tool name 'save_settings' with description 'Save current settings to EEPROM' - persists configuration changes to non-volatile memory on a flight controller, modifying the drone's operational parameters.
Attacks that exploit this kind of access
Save current settings to EEPROM. Call this after making changes. 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 save_settings: 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.
save_settings 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 save_settings 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 save_settings. 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.
save_settings 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 →