Dump the complete UI hierarchy of the current screen as XML. Essential for understanding screen structure, finding elements, and debugging automation issues.
AI agents call dump_hierarchy to retrieve information from MCP Android Agent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns the UI hierarchy of the current screen as XML data. It has no side effects—it only reads/captures the current screen structure. However, severity is medium because the UI hierarchy can expose sensitive information displayed on screen (passwords, personal data, app content) to an AI agent.
From the tool's definition Dump the complete UI hierarchy of the current screen as XML
Documented attack patterns abuse exactly the kind of access dump_hierarchy gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Android Agent, and nothing reaches the server without passing your rules. This is the rule we recommend for dump_hierarchy:
{
"version": "1",
"default": "deny",
"tools": {
"dump_hierarchy": {}
}
}dump_hierarchy 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.
Dump the complete UI hierarchy of the current screen as XML. Essential for understanding screen structure, finding elements, and debugging automation issues. It is categorised as a Read tool in the MCP Android Agent MCP Server, which means it retrieves data without modifying state.
Register the MCP Android Agent 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 MCP Android Agent. 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 MCP Android Agent MCP server (nim444/mcp-android-server-python). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 28 MCP Android Agent tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
28 MCP Android Agent tools catalogued and risk-classified — across an index of 42,500+ MCP servers.