AI agents call adb_list_devices to retrieve information from LocalAnt without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation: it queries and returns a list of connected Android devices. There are no side effects, no code execution, no data modification, and no irreversible actions. The blast radius is minimal—an agent listing devices gains situational awareness but cannot directly harm the system or data without using other tools. This is a classic Read category operation.
From the tool's definition Tool name 'adb_list_devices' and description 'List connected Android devices' indicate a query operation that retrieves information about connected devices without modification or execution of commands on those devices.
Attacks that exploit this kind of access
List connected Android devices. It is categorised as a Read tool in the LocalAnt MCP Server, which means it retrieves data without modifying state.
Register the LocalAnt MCP server in PolicyLayer and add a rule for adb_list_devices: 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 LocalAnt. Nothing to install.
adb_list_devices 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 adb_list_devices 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 adb_list_devices. 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.
adb_list_devices is provided by the LocalAnt MCP server (yuga-hashimoto/localant). 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 →