Uninstall an app by package. Requires approval (risk 3).
AI agents call adb_uninstall to permanently remove resources in LocalAnt — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Uninstalling an application is a destructive operation that cannot be easily undone without reinstalling the app. While not as severe as data deletion, it permanently removes software from the device, affecting system state irreversibly. The explicit risk-3 approval requirement supports the destructive categorization. This exceeds Write (which is reversible) and falls squarely into Destructive.
From the tool's definition Tool name 'adb_uninstall' and description 'Uninstall an app by package' directly indicate irreversible removal of software. The 'Requires approval (risk 3)' annotation confirms high-risk classification.
Attacks that exploit this kind of access
Uninstall an app by package. Requires approval (risk 3). It is categorised as a Destructive tool in the LocalAnt MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the LocalAnt 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 LocalAnt. 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 LocalAnt MCP server (yuga-hashimoto/localant). 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 →