Clear text from a UI element by resource ID
AI agents invoke android_uiautomator_clear_text to trigger actions in Android MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Clearing text from a UI element via UIAutomator is an active device interaction that executes an automation command against the Android device. It modifies the current state of a UI element (removes text), which could be a form field, search box, or other input.
From the tool's definition 'Clear text from a UI element by resource ID' — this triggers a UI automation action on the Android device that modifies the state of a UI element by removing its text content
Attacks that exploit this kind of access
Clear text from a UI element by resource ID. It is categorised as a Execute tool in the Android MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Android MCP Server MCP server in PolicyLayer and add a rule for android_uiautomator_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 Android MCP Server. Nothing to install.
android_uiautomator_clear_text is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the android_uiautomator_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 android_uiautomator_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.
android_uiautomator_clear_text is provided by the Android MCP Server MCP server (jduartedj/android-mcp-server). 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 →