Get list of enabled/disabled features (AIRMODE, OSD, GPS, etc.)
AI agents call get_features 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 only reads and returns the status of flight controller features. It has no side effects, performs no modifications, executes no commands, and creates no obligations. It is a straightforward data retrieval operation appropriate for the Read category. Severity is low because exposure of feature configuration state poses minimal risk—this information is typically non-sensitive operational metadata.
From the tool's definition Tool name 'get_features' and description 'Get list of enabled/disabled features' indicate a query operation that retrieves current configuration state without modifying or executing any actions.
Attacks that exploit this kind of access
Get list of enabled/disabled features (AIRMODE, OSD, GPS, etc.). 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_features: 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_features 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_features 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_features. 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_features 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 →