adb_shell_command
Execute a whitelisted shell command on the Android device.
This record as markdown: /tools/0x-professor-droidforensics-suite/adb-shell-command.md
What adb_shell_command does on Android Forensics ADB MCP Server
AI agents invoke adb_shell_command to trigger actions in Android Forensics 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.
Why adb_shell_command is rated High
This tool executes shell commands on an Android device, which is a classic Execute pattern: it triggers external operations (shell execution) whose effects depend on arguments and can cause side effects ranging from data extraction to system modification. While a whitelist mitigates some risk, shell commands can still be used to trigger destructive operations, exfiltrate data, or compromise device integrity.
From the tool's definition 'Execute a whitelisted shell command on the Android device' – the tool directly runs shell commands on a target device, enabling arbitrary code execution within the constraint of a whitelist.
Attacks that exploit this kind of access
The rule that runs adb_shell_command safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Android Forensics ADB MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_shell_command, this is the rule to start with:
adb_shell_command stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Android Forensics ADB MCP Server, apply this rule, and every adb_shell_command call is checked against it from then on.
Questions about adb_shell_command
Execute a whitelisted shell command on the Android device. It is categorised as a Execute tool in the Android Forensics ADB MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Android Forensics ADB MCP Server MCP server in PolicyLayer and add a rule for adb_shell_command: 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 Android Forensics ADB MCP Server. Nothing to install.
adb_shell_command 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_command 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_command. 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_command is provided by the Android Forensics ADB MCP Server MCP server (0x-professor/droidforensics-suite). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Android Forensics ADB MCP Server, and thousands of servers like it.
Across the catalogue