Execute an Android shell command. ⚠️ Requires confirm=true.
AI agents invoke adb_shell to trigger actions in ADB MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool allows arbitrary shell command execution on Android devices, which can manipulate system state, install/modify software, access sensitive data, and trigger potentially irreversible actions depending on command arguments.
From the tool's definition Tool explicitly enables 'Execute an Android shell command' with arbitrary command execution capability, requires confirmation flag suggesting high-risk nature. Server description mentions 'shell execution' as a core capability.
Attacks that exploit this kind of access
Execute an Android shell command. ⚠️ Requires confirm=true. It is categorised as a Execute tool in the ADB MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ADB MCP Server MCP server in PolicyLayer and add a rule for adb_shell: 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_shell is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the adb_shell 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_shell. 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_shell is provided by the ADB MCP Server MCP server (lll-404/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 →