Get full RC tuning: per-axis rates, expo, TPA, rates_type
AI agents call get_rc_tuning_full to retrieve information from Betaflight MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves configuration parameters (rates, expo, TPA, rates_type) from the flight controller for inspection. It performs no write operations, does not execute commands with side effects, does not delete data, and does not involve financial transactions. The action is purely informational querying of drone tuning settings.
From the tool's definition Tool name 'get_rc_tuning_full' explicitly uses 'get' verb and description states 'Get full RC tuning: per-axis rates, expo, TPA, rates_type' — pure data retrieval with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get full RC tuning: per-axis rates, expo, TPA, rates_type. It is categorised as a Read tool in the Betaflight MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Betaflight MCP Server MCP server in PolicyLayer and add a rule for get_rc_tuning_full: 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.
get_rc_tuning_full is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_rc_tuning_full 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 get_rc_tuning_full. 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.
get_rc_tuning_full 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 →