android_run_shell · DevLab MCP Suite MCP: Risk & Policy

WHAT IT DOES

What android_run_shell does on DevLab MCP Suite

AI agents invoke android_run_shell to trigger actions in DevLab MCP Suite. 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_run_shell needs a policy

Executing shell commands on an Android device is inherently an Execute operation—the effects depend entirely on the arguments provided. While individual commands may be benign, an AI agent could easily compose commands that read sensitive data, modify system state, exfiltrate information, or launch denial-of-service attacks.

From the tool's definition Tool description states "run a simple adb shell command on the connected Android device." The ability to execute arbitrary shell commands is a core Execute action.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

android_run_shell Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "android_run_shell": {
      "limits": [
        {
          "counter": "android_run_shell_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 DevLab MCP Suite, so you can run agents against it safely.

FAQ

Questions about android_run_shell

What does the android_run_shell tool do? +

Advanced tool: run a simple adb shell command on the connected Android device. It is categorised as a Execute tool in the DevLab MCP Suite 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_run_shell? +

Register the DevLab MCP Suite MCP server in PolicyLayer and add a rule for android_run_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 DevLab MCP Suite. Nothing to install.

What risk level is android_run_shell? +

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

Can I rate-limit android_run_shell? +

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

How do I block android_run_shell completely? +

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

What MCP server provides android_run_shell? +

android_run_shell is provided by the DevLab MCP Suite MCP server (tanguito86/devlab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.