Copy PID settings from one profile to another
AI agents use copy_pid_profile 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 creates or modifies PID profile data on the flight controller. While the operation is reversible (profiles can be restored from backup or edited), it alters active configuration that directly affects drone flight behavior. PID tuning errors could cause unstable flight, crashes, or loss of vehicle control.
From the tool's definition 'Copy PID settings from one profile to another' modifies configuration data by duplicating PID profiles, which are reversible changes to drone flight controller settings.
Attacks that exploit this kind of access
Copy PID settings from one profile to another. 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 copy_pid_profile: 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.
copy_pid_profile 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 copy_pid_profile 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 copy_pid_profile. 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.
copy_pid_profile 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 →