Uninstall an app from the Android box by package name.
AI agents call uninstall_apk to permanently remove resources in Android Tester MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Uninstalling an APK permanently removes an application and its associated data from the Android device. This action cannot be easily undone without reinstalling the app, making it a destructive operation. While not as severe as data deletion, it irreversibly alters the device state.
From the tool's definition Tool name 'uninstall_apk' combined with description 'Uninstall an app from the Android box by package name' indicates irreversible removal of application data and installation.
Attacks that exploit this kind of access
Uninstall an app from the Android box by package name. It is categorised as a Destructive tool in the Android Tester MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Android Tester MCP server in PolicyLayer and add a rule for uninstall_apk: 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 Tester MCP. Nothing to install.
uninstall_apk 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_apk 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_apk. 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_apk is provided by the Android Tester MCP server (zhenweiwang1990/android-tester-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 →