Detectar si el TBS Tango 2 está conectado por USB y encontrar el punto de montaje.
AI agents call detect_radio 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 performs device detection and queries system state to discover whether a radio controller is connected and where it is mounted. It retrieves information without creating, modifying, deleting, or executing any operations. No side effects or changes to the system occur. This is a pure read operation.
From the tool's definition Tool name 'detect_radio' and description 'Detectar si el TBS Tango 2 está conectado por USB y encontrar el punto de montaje' (Detect if TBS Tango 2 is connected via USB and find the mount point) — this queries the connection status and mount point of a USB…
Attacks that exploit this kind of access
Detectar si el TBS Tango 2 está conectado por USB y encontrar el punto de montaje. 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 detect_radio: 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.
detect_radio 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 detect_radio 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 detect_radio. 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.
detect_radio 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 →