Get detailed reasons why the drone cannot arm
AI agents call get_arming_disable_flags 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 and reports diagnostic information about the current state of arming disable flags. It has no side effects, does not execute operations, and does not modify configuration or state. It is purely informational, making it a Read category tool with low severity since misuse would only expose status data without enabling harmful actions on the drone.
From the tool's definition Tool name 'get_arming_disable_flags' and description 'Get detailed reasons why the drone cannot arm' indicate a query/retrieval operation that returns status information about arming conditions without modifying any state or triggering actions.
Attacks that exploit this kind of access
Get detailed reasons why the drone cannot arm. 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_arming_disable_flags: 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_arming_disable_flags 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_arming_disable_flags 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_arming_disable_flags. 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_arming_disable_flags 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 →