adb_shell

Execute a shell command on the Android device. Returns stdout and stderr.

SERVERDeepadb SOURCEdeepadb

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-fullread-deepadb/adb-shell.md

WHAT IT DOES

What adb_shell does on Deepadb

AI agents invoke adb_shell to trigger actions in Deepadb. 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.

RISK

Why adb_shell is rated High

This tool permits execution of arbitrary shell commands on an Android device with effects entirely dependent on the command arguments. Shell execution is inherently high-impact: an agent could read sensitive data, modify system state, install malware, exfiltrate credentials, or compromise device security. The blast radius is maximal because any shell command is possible.

From the tool's definition Tool name 'adb_shell' and description 'Execute a shell command on the Android device' directly indicate arbitrary shell command execution capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs adb_shell safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Deepadb, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_shell, this is the rule to start with:

adb_shell Rate-limited

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.

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Deepadb, apply this rule, and every adb_shell call is checked against it from then on.

FAQ

Questions about adb_shell

What does the adb_shell tool do? +

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

How do I enforce a policy on adb_shell? +

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

What risk level is adb_shell? +

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

Can I rate-limit adb_shell? +

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

How do I block adb_shell completely? +

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

What MCP server provides adb_shell? +

adb_shell is provided by the Deepadb MCP server (deepadb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Deepadb, and thousands of servers like it.

This server

All 205 Deepadb tools → High-risk tools on this server →

Across the catalogue

adb_shell_command on Android Forensics ADB MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →