adb_rm
Delete a file or directory on the device. Recursive deletion uses depth-based protection: refuses at depth ≤ 2 from root (blocks rm -rf /system or /sdcard but allows /sdcard/project/build/). Symlinks are resolved before depth checks to prevent traversal bypasses. Hard-blocks /dev, /proc, /sys. Fo...
This record as markdown: /tools/io-github-fullread-deepadb/adb-rm.md
What adb_rm does on Deepadb
AI agents call adb_rm to permanently remove resources in Deepadb, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why adb_rm is rated Critical
The adb_rm tool irreversibly deletes files and directories on an Android device. While the tool includes safeguards (depth-based protection, hard-blocks on system directories), deletion is fundamentally irreversible and destructive. Although guardrails reduce the blast radius compared to unrestricted rm, the core action remains destructive.
From the tool's definition Delete a file or directory on the device. Recursive deletion... Hard-blocks /dev, /proc, /sys.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs adb_rm 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_rm, this is the rule to start with:
adb_rm is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Deepadb, apply this rule, and every adb_rm call is checked against it from then on.
Questions about adb_rm
Delete a file or directory on the device. Recursive deletion uses depth-based protection: refuses at depth ≤ 2 from root (blocks rm -rf /system or /sdcard but allows /sdcard/project/build/). Symlinks are resolved before depth checks to prevent traversal bypasses. Hard-blocks /dev, /proc, /sys. For recursive deletes, reports a pre-flight file count. It is categorised as a Destructive tool in the Deepadb MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Deepadb MCP server in PolicyLayer and add a rule for adb_rm: 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.
adb_rm is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the adb_rm 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.
Set action: deny in the PolicyLayer policy for adb_rm. 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.
adb_rm 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.
Across the catalogue