adb_a11y_tree
Dump the accessibility-focused view of the UI hierarchy. Shows only elements relevant to screen readers: their roles, labels, states, and navigation order. Filters out decorative/layout containers.
This record as markdown: /tools/io-github-fullread-deepadb/adb-a11y-tree.md
What adb_a11y_tree does on Deepadb
AI agents call adb_a11y_tree to retrieve information from Deepadb without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why adb_a11y_tree is rated Low
This tool performs a query/inspection of the device's UI accessibility tree. It retrieves information about screen reader-relevant elements (roles, labels, states, navigation order) but does not modify, execute, delete, or trigger external actions. The blast radius of misuse is minimal—it only exposes UI metadata that an accessibility tool would normally surface. No financial or destructive impact is possible.
From the tool's definition Tool description states "Dump the accessibility-focused view of the UI hierarchy" and "Shows only elements relevant to screen readers" — these are read operations that retrieve and display UI structure without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
The rule that runs adb_a11y_tree safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Deepadb, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_a11y_tree, this is the rule to start with:
adb_a11y_tree is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Deepadb, apply this rule, and every adb_a11y_tree call is checked against it from then on.
Questions about adb_a11y_tree
Dump the accessibility-focused view of the UI hierarchy. Shows only elements relevant to screen readers: their roles, labels, states, and navigation order. Filters out decorative/layout containers. It is categorised as a Read tool in the Deepadb MCP Server, which means it retrieves data without modifying state.
Register the Deepadb MCP server in PolicyLayer and add a rule for adb_a11y_tree: 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 Deepadb. Nothing to install.
adb_a11y_tree 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 adb_a11y_tree 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 adb_a11y_tree. 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.
adb_a11y_tree is provided by the Deepadb MCP server (deepadb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Deepadb, and thousands of servers like it.
This server
Across the catalogue