AI agents call xpath_exists to retrieve information from uiautomator2 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name 'xpath_exists' implies querying the UI hierarchy to determine if an element matching an XPath expression is present. This is a read-only inspection operation. The description is empty, which lowers confidence, but the naming convention strongly suggests a non-destructive query. Severity is low as misuse would only result in incorrect UI state detection.
From the tool's definition Tool name 'xpath_exists' suggests checking for the existence of a UI element via XPath selector — a read/query operation with no side effects.
Documented attack patterns abuse exactly the kind of access xpath_exists 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_exists:
{
"version": "1",
"default": "deny",
"tools": {
"xpath_exists": {}
}
}xpath_exists is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
xpath_exists. It is categorised as a Read tool in the uiautomator2 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the uiautomator2 MCP Server MCP server in PolicyLayer and add a rule for xpath_exists: 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_exists is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the xpath_exists 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_exists. 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_exists 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.