android_execute_command · Android MCP Server MCP

WHAT IT DOES

What android_execute_command does on Android MCP Server

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

Why android_execute_command needs a policy

This tool permits execution of arbitrary ADB (Android Debug Bridge) commands with user-supplied parameters. ADB commands can install/uninstall apps, modify system settings, access sensitive data, install malware, factory reset devices, and execute shell code with device privileges. The 'generic' and 'any' language confirms unrestricted execution capability.

From the tool's definition Tool description states 'Execute a generic ADB command with custom arguments. Allows agents to run any ADB command with their own parameters.' The use of 'Execute', 'generic', 'any ADB command', and 'custom arguments' indicates arbitrary command execution…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

android_execute_command Rate-limited

android_execute_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": {
    "android_execute_command": {
      "limits": [
        {
          "counter": "android_execute_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 MCP Server, so you can run agents against it safely.

FAQ

Questions about android_execute_command

What does the android_execute_command tool do? +

Execute a generic ADB command with custom arguments. Allows agents to run any ADB command with their own parameters. It is categorised as a Execute tool in the Android MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on android_execute_command? +

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

What risk level is android_execute_command? +

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

Can I rate-limit android_execute_command? +

Yes. Add a rate_limit block to the android_execute_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 android_execute_command completely? +

Set action: deny in the PolicyLayer policy for android_execute_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 android_execute_command? +

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