adb_root_shell

Execute a command as root via su. Requires rooted device.

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-root-shell.md

What adb_root_shell does on Deepadb

AI agents invoke adb_root_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.

Why adb_root_shell is rated High

This tool allows running arbitrary shell commands with root-level permissions on an Android device. The blast radius is maximal: an AI agent could use this to modify system files, install malware, exfiltrate data, disable security controls, or perform any destructive action on the device.

From the tool's definition "Execute a command as root via su. Requires rooted device." — This tool directly executes arbitrary commands with root privileges on the target device.

Risk signalsAdmin/system-level operation

Questions about adb_root_shell

What does the adb_root_shell tool do? +

Execute a command as root via su. Requires rooted device. 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_root_shell? +

Register the Deepadb MCP server in PolicyLayer and add a rule for adb_root_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_root_shell? +

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

Can I rate-limit adb_root_shell? +

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

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

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

More on Deepadb, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Deepadb's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.