Get battery voltage, current draw, mAh consumed, and RSSI
AI agents call get_battery_status 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 queries and returns real-time sensor data from the drone's battery monitoring system. It performs no write, delete, execute, or financial operations. The worst-case misuse would be an agent repeatedly polling this data, which has negligible impact. Classification as Read with low severity is appropriate.
From the tool's definition Tool name is 'get_battery_status' and description states it retrieves 'battery voltage, current draw, mAh consumed, and RSSI' — all telemetry readings with no modification or side effects.
Attacks that exploit this kind of access
Get battery voltage, current draw, mAh consumed, and RSSI. 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_battery_status: 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_battery_status 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_battery_status 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_battery_status. 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_battery_status 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 →