Dump the current UI hierarchy as XML.
AI agents call dump_hierarchy to retrieve information from Android MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and returns the current state of the UI as XML data. It has no side effects — it only retrieves information about the UI hierarchy without modifying anything on the device.
From the tool's definition Dump the current UI hierarchy as XML
Attacks that exploit this kind of access
Dump the current UI hierarchy as XML. It is categorised as a Read tool in the Android MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Android MCP Server MCP server in PolicyLayer and add a rule for dump_hierarchy: 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.
dump_hierarchy 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 dump_hierarchy 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 dump_hierarchy. 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.
dump_hierarchy is provided by the Android MCP Server MCP server (itest4u/android-mcp). 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 →