AI agents call clear_text 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.
Text clearing in UI automation is destructive because it permanently removes data from input fields without user confirmation or undo capability. While the blast radius depends on what text field is targeted, the irreversible nature of data deletion justifies the Destructive category and high severity. Confidence is reduced (0.85 not 0.95) due to the empty description leaving some ambiguity about exact behavior.
From the tool's definition Tool name 'clear_text' on an Android UI automation server with capabilities to tap, swipe, and manage apps.
Documented attack patterns abuse exactly the kind of access clear_text 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 clear_text:
{
"version": "1",
"default": "deny",
"hide": [
"clear_text"
]
}clear_text 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.
clear_text. 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 clear_text: 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.
clear_text 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 clear_text 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 clear_text. 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.
clear_text 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.