Uninstalls an application from a connected Android device
AI agents call adb_uninstall to permanently remove resources in Android ADB MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Uninstalling an application permanently removes the app, its data, and associated files from the device. This is an irreversible action that destroys data and application state. While not as critical as dropping a database, it represents a destructive operation with significant impact on device functionality and user data.
From the tool's definition Tool name is 'adb_uninstall' and description states it 'Uninstalls an application from a connected Android device' — uninstallation is an irreversible removal of application data and files that cannot be undone without reinstalling from scratch.
Documented attack patterns abuse exactly the kind of access adb_uninstall gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Android ADB MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for adb_uninstall:
{
"version": "1",
"default": "deny",
"hide": [
"adb_uninstall"
]
} adb_uninstall 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.
Uninstalls an application from a connected Android device. It is categorised as a Destructive tool in the Android ADB MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Android ADB MCP Server MCP server in PolicyLayer and add a rule for adb_uninstall: 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 Android ADB MCP Server. Nothing to install.
adb_uninstall 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_uninstall 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_uninstall. 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_uninstall is provided by the Android ADB MCP Server MCP server (landicefu/android-adb-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Android 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.
10 Android ADB MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.