Uninstall an APP from an Android device.
AI agents call uninstall_app to permanently remove resources in Android Device — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Uninstalling an app is a destructive operation that irreversibly removes application files, data, and configurations from the device. While it can technically be reversed by reinstalling, the immediate action destroys the installed application state. This is more severe than Write (which is reversible) and qualifies as Destructive.
From the tool's definition Tool name 'uninstall_app' combined with description 'Uninstall an APP from an Android device' indicates irreversible removal of application data and binaries from the device.
Attacks that exploit this kind of access
Uninstall an APP from an Android device. It is categorised as a Destructive tool in the Android Device MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Android Device MCP server in PolicyLayer and add a rule for uninstall_app: 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 Device. Nothing to install.
uninstall_app 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 uninstall_app 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 uninstall_app. 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.
uninstall_app is provided by the Android Device MCP server (prashant1507/android-device-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →