Get detailed battery statistics
AI agents call get_battery_stats to retrieve information from Enhanced ADB 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 battery telemetry data from an Android device via ADB. It has no side effects, does not modify device state, and does not execute commands or operations. It is purely informational, making it a Read category risk. Severity is low because battery statistics are non-sensitive system information with minimal impact if exposed to unauthorized access.
From the tool's definition Tool name 'get_battery_stats' and description 'Get detailed battery statistics' indicate a read-only query operation that retrieves device battery information without modifying or executing any actions.
Attacks that exploit this kind of access
Get detailed battery statistics. It is categorised as a Read tool in the Enhanced ADB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Enhanced ADB MCP Server MCP server in PolicyLayer and add a rule for get_battery_stats: 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 Enhanced ADB MCP Server. Nothing to install.
get_battery_stats 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_stats 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_stats. 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_stats is provided by the Enhanced ADB MCP Server MCP server (rahulkr/r_adb_mcp_server). 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 →