Set RC tuning parameter (rates, expo, TPA).
AI agents use set_rc_tuning 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 creates or modifies RC (remote control) tuning parameters, which are persistent configuration settings on the flight controller. These changes affect how the drone responds to pilot inputs and are reversible via backup/restore operations. This is a Write operation (configuration modification) rather than Execute (which would invoke one-time commands).
From the tool's definition Tool description states 'Set RC tuning parameter (rates, expo, TPA)' — this modifies drone flight controller configuration parameters that directly affect aircraft control behavior.
Attacks that exploit this kind of access
Set RC tuning parameter (rates, expo, TPA). 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 set_rc_tuning: 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.
set_rc_tuning 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 set_rc_tuning 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 set_rc_tuning. 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.
set_rc_tuning 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 →