AI agents call dump_ui_hierarchy to retrieve information from Adb without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries the current state of the Android UI hierarchy for inspection purposes. It has no side effects on the device state, does not modify or delete data, and does not trigger external operations. It is purely a diagnostic/inspection capability, consistent with Read category operations like 'get', 'fetch', or 'query'.
From the tool's definition Tool name 'dump_ui_hierarchy' and description '获取界面层次结构' (retrieve UI hierarchy structure) indicate querying/retrieving UI element information with no data modification, deletion, or external operations.
Documented attack patterns abuse exactly the kind of access dump_ui_hierarchy gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Adb, and nothing reaches the server without passing your rules. This is the rule we recommend for dump_ui_hierarchy:
{
"version": "1",
"default": "deny",
"tools": {
"dump_ui_hierarchy": {}
}
}dump_ui_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.
获取界面层次结构. It is categorised as a Read tool in the Adb MCP Server, which means it retrieves data without modifying state.
Register the Adb MCP server in PolicyLayer and add a rule for dump_ui_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 Adb. Nothing to install.
dump_ui_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_ui_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_ui_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_ui_hierarchy is provided by the Adb MCP server (wolfcoming/adb_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Adb, 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.
48 Adb tools catalogued and risk-classified — across an index of 43,000+ MCP servers.