Remove pacote Android via adb uninstall.
AI agents call adb_uninstall to permanently remove resources in AVD MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently uninstalls packages from an Android Virtual Device, which cannot be undone without reinstalling. While the impact is scoped to the emulator environment, the irreversible nature of package removal and the potential to break development workflows or delete user data within those packages classifies this as Destructive.
From the tool's definition Tool name 'adb_uninstall' combined with description 'Remove pacote Android via adb uninstall' indicates irreversible deletion of Android packages/applications from a device.
Attacks that exploit this kind of access
Remove pacote Android via adb uninstall. It is categorised as a Destructive tool in the AVD MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AVD 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 AVD 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 AVD MCP Server MCP server (jramalho/avd-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 →