AI agents call rm to permanently remove resources in ADB MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs irreversible deletion of files on an Android device. Once executed, deleted files cannot be recovered through normal means. This is a destructive operation that permanently removes data. While the blast radius is somewhat limited to a single device's filesystem (not system-wide), the irreversibility and potential to delete critical app data, system files, or user data justifies 'high' severity.
From the tool's definition Tool name 'rm' with description 'Remove a file from the Android device' - rm is the standard Unix command for irreversible file deletion.
Documented attack patterns abuse exactly the kind of access rm gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ADB MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for rm:
{
"version": "1",
"default": "deny",
"hide": [
"rm"
]
}rm disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove a file from the Android device. It is categorised as a Destructive tool in the ADB MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ADB MCP Server MCP server in PolicyLayer and add a rule for 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 ADB MCP Server. Nothing to install.
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 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 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.
rm is provided by the ADB MCP Server MCP server (jiantao88/android-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ADB MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
30 ADB MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.