execute_shell_command · Android Device MCP: Risk & Policy

WHAT IT DOES

What execute_shell_command does on Android Device

AI agents invoke execute_shell_command to trigger actions in Android Device. 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 IT NEEDS A POLICY

Why execute_shell_command needs a policy

Executing shell commands on a device is a classic Execute category action—it triggers external operations (on the Android system) whose effects depend entirely on the arguments passed. The severity is critical because shell command execution grants near-unlimited capabilities: an attacker could read sensitive data, modify system files, install malware, exfiltrate information, or compromise the entire device.

From the tool's definition Tool name is 'execute_shell_command' and description states 'Execute shell command in an Android device.' This directly runs arbitrary commands on a connected Android device via ADB.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_shell_command Rate-limited

execute_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute_shell_command": {
      "limits": [
        {
          "counter": "execute_shell_command_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Android Device, so you can run agents against it safely.

FAQ

Questions about execute_shell_command

What does the execute_shell_command tool do? +

Execute shell command in an Android device. It is categorised as a Execute tool in the Android Device MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_shell_command? +

Register the Android Device MCP server in PolicyLayer and add a rule for execute_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 Device. Nothing to install.

What risk level is execute_shell_command? +

execute_shell_command is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit execute_shell_command? +

Yes. Add a rate_limit block to the execute_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.

How do I block execute_shell_command completely? +

Set action: deny in the PolicyLayer policy for execute_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.

What MCP server provides execute_shell_command? +

execute_shell_command is provided by the Android Device MCP server (prashant1507/android-device-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.