AI agents call purge to permanently remove resources in uiautomator2 MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool name 'purge' inherently implies irreversible data deletion or complete removal. While the description is empty (lowering confidence slightly), the name alone and the Android automation context strongly suggest destructive capability. If this tool removes app data, cache, or system files without undo capability, it cannot be recovered.
From the tool's definition Tool name 'purge' combined with uiautomator2 context (Android device automation) suggests irreversible deletion or clearing of data. Sibling tools like 'app_clear' and 'app_install' indicate this server manages app and system state.
Documented attack patterns abuse exactly the kind of access purge gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and uiautomator2 MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for purge:
{
"version": "1",
"default": "deny",
"hide": [
"purge"
]
}purge 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.
purge. It is categorised as a Destructive tool in the uiautomator2 MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the uiautomator2 MCP Server MCP server in PolicyLayer and add a rule for purge: 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 uiautomator2 MCP Server. Nothing to install.
purge 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 purge 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 purge. 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.
purge is provided by the uiautomator2 MCP Server MCP server (tanbro/uiautomator2-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from uiautomator2 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.
77 uiautomator2 MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.