Get VTX (video transmitter) settings (band, channel, power)
AI agents call get_vtx_config 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 from the video transmitter without modifying any state or triggering external actions. It has no side effects and presents minimal risk if misused by an AI agent—at worst, it returns information already accessible to the operator. The low blast radius and purely informational nature place it in the Read category with low severity.
From the tool's definition Tool name 'get_vtx_config' and description 'Get VTX (video transmitter) settings (band, channel, power)' indicate data retrieval only. The verb 'Get' and absence of modification language confirm read-only operation.
Attacks that exploit this kind of access
Get VTX (video transmitter) settings (band, channel, power). 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_vtx_config: 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_vtx_config 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_vtx_config 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_vtx_config. 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_vtx_config 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 →