Check if ADB (Android Debug Bridge) is available in the system PATH and list all connected Android devices with their status
AI agents call check_adb_and_list_devices to retrieve information from MCP Android Agent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and reports data about system state (ADB availability) and device inventory (connected devices and their status) with no side effects. It is purely diagnostic/informational in nature, analogous to status checks and queries. While it operates in a privileged domain (Android debugging), the tool itself only gathers information, making it a Read category risk.
From the tool's definition The tool 'check_adb_and_list_devices' performs informational queries: it checks ADB availability in the system PATH and lists connected Android devices with their status.
Documented attack patterns abuse exactly the kind of access check_adb_and_list_devices gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Android Agent, and nothing reaches the server without passing your rules. This is the rule we recommend for check_adb_and_list_devices:
{
"version": "1",
"default": "deny",
"tools": {
"check_adb_and_list_devices": {}
}
}check_adb_and_list_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.
Check if ADB (Android Debug Bridge) is available in the system PATH and list all connected Android devices with their status. It is categorised as a Read tool in the MCP Android Agent MCP Server, which means it retrieves data without modifying state.
Register the MCP Android Agent MCP server in PolicyLayer and add a rule for check_adb_and_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 MCP Android Agent. Nothing to install.
check_adb_and_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 check_adb_and_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 check_adb_and_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.
check_adb_and_list_devices is provided by the MCP Android Agent MCP server (nim444/mcp-android-server-python). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 28 MCP Android Agent tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
28 MCP Android Agent tools catalogued and risk-classified — across an index of 42,500+ MCP servers.