Executes a raw ADB shell command on the connected Android device and returns the output. Requires the command parameter, which is the shell command to execute.
AI agents invoke execute_adb_shell to trigger actions in Ultimate Android MCP. 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 execution of arbitrary shell commands on an Android device with no restrictions evident from the description. Shell command execution is a classic Execute category risk, and the 'raw' qualifier emphasizes that any command can be passed.
From the tool's definition Executes a raw ADB shell command on the connected Android device and returns the output. Requires the `command` parameter, which is the shell command to execute.
Documented attack patterns abuse exactly the kind of access execute_adb_shell gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ultimate Android MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for execute_adb_shell:
{
"version": "1",
"default": "deny",
"tools": {
"execute_adb_shell": {
"limits": [
{
"counter": "execute_adb_shell_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}execute_adb_shell 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.
Free to start. No card required.
Executes a raw ADB shell command on the connected Android device and returns the output. Requires the command parameter, which is the shell command to execute. It is categorised as a Execute tool in the Ultimate Android MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ultimate Android MCP server in PolicyLayer and add a rule for execute_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 Ultimate Android MCP. Nothing to install.
execute_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 execute_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 execute_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.
execute_adb_shell is provided by the Ultimate Android MCP server (oddlyspaced/ultimate-android-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ultimate Android MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
35 Ultimate Android MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.