Get current RC channel values from the receiver
AI agents call get_rc_channels 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 the current state of RC (remote control) channel inputs from the drone's receiver. It performs a query/fetch operation with no capability to modify configuration, execute commands, or cause irreversible changes. The severity is low because reading channel values poses minimal risk—an AI agent obtaining this telemetry cannot harm the drone or user through data retrieval alone.
From the tool's definition Tool name 'get_rc_channels' combined with description 'Get current RC channel values from the receiver' indicates data retrieval without modification or side effects.
Attacks that exploit this kind of access
Get current RC channel values from the receiver. 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_channels: 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_channels 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_channels 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_channels. 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_channels 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 →