AI agents invoke xpath_wait_gone 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 appears to wait for an XPath-identified UI element to become absent from the device's screen. While the empty description reduces confidence, the naming convention and context of an Android automation server indicate this performs a triggered detection/wait operation on a live device, classifying it as Execute rather than Read.
From the tool's definition Tool name 'xpath_wait_gone' combined with sibling tools like 'activity_wait_appear', 'app_auto_grant_permissions', 'app_start', 'app_stop' and server description indicating UI automation control via uiautomator2.
Documented attack patterns abuse exactly the kind of access xpath_wait_gone 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 xpath_wait_gone:
{
"version": "1",
"default": "deny",
"tools": {
"xpath_wait_gone": {
"limits": [
{
"counter": "xpath_wait_gone_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}xpath_wait_gone 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.
xpath_wait_gone. 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 xpath_wait_gone: 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.
xpath_wait_gone 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 xpath_wait_gone 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 xpath_wait_gone. 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.
xpath_wait_gone 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.