AI agents invoke activity_wait_appear to trigger actions in uiautomator2 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.
This tool executes an operation that interacts with an Android device's runtime state (waiting for an activity to appear), triggering external side effects. While the description is empty (reducing confidence slightly), the context of uiautomator2 and the tool name make it clear this performs automation/execution rather than simple data retrieval.
From the tool's definition Tool name 'activity_wait_appear' is part of uiautomator2, which is an Android automation framework. The sibling tools confirm this server controls Android devices via actions like tapping, swiping, and app management.
Documented attack patterns abuse exactly the kind of access activity_wait_appear 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 activity_wait_appear:
{
"version": "1",
"default": "deny",
"tools": {
"activity_wait_appear": {
"limits": [
{
"counter": "activity_wait_appear_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}activity_wait_appear stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
activity_wait_appear. It is categorised as a Execute tool in the uiautomator2 MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the uiautomator2 MCP Server MCP server in PolicyLayer and add a rule for activity_wait_appear: 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.
activity_wait_appear 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 activity_wait_appear 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 activity_wait_appear. 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.
activity_wait_appear 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.