AI agents call adb_devices to retrieve information from ADB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The ADB 'adb devices' command is a standard read-only operation that lists connected devices. No modification, execution, or deletion of data occurs. Empty description lowers confidence slightly, but the tool name strongly implies a read/list operation.
From the tool's definition Tool name 'adb_devices' with empty description; based on ADB context, this command lists connected Android devices without side effects.
Documented attack patterns abuse exactly the kind of access adb_devices gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ADB MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for adb_devices:
{
"version": "1",
"default": "deny",
"tools": {
"adb_devices": {}
}
}adb_devices is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
adb_devices. It is categorised as a Read tool in the ADB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ADB MCP Server MCP server in PolicyLayer and add a rule for adb_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 ADB MCP Server. Nothing to install.
adb_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_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_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_devices is provided by the ADB MCP Server MCP server (srmorete/adb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 10 ADB MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
10 ADB MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.