ui_traverse
Breadth-first traversal of the accessibility tree. Returns a flat list of all UI elements
This record as markdown: /tools/io-github-heznpc-iconnect/ui-traverse.md
What ui_traverse does on Iconnect
AI agents call ui_traverse to retrieve information from Iconnect without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why ui_traverse is rated Low
The tool performs passive introspection of the accessibility tree to enumerate UI elements. This is informational (Read category) with minimal risk — it retrieves data about the user interface state but has no side effects. Severity is low because misuse would expose UI structure information but cannot directly harm data or systems. Confidence is high because the description is clear and unambiguous.
From the tool's definition Tool name is 'ui_traverse' and description states 'Breadth-first traversal of the accessibility tree. Returns a flat list of all UI elements' — this is a query/inspection operation that retrieves information about UI structure without modifying, executing, or…
Attacks that exploit this kind of access
The rule that runs ui_traverse safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ui_traverse, this is the rule to start with:
ui_traverse 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 Iconnect, apply this rule, and every ui_traverse call is checked against it from then on.
Questions about ui_traverse
Breadth-first traversal of the accessibility tree. Returns a flat list of all UI elements. It is categorised as a Read tool in the Iconnect MCP Server, which means it retrieves data without modifying state.
Register the Iconnect MCP server in PolicyLayer and add a rule for ui_traverse: 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 Iconnect. Nothing to install.
ui_traverse 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 ui_traverse 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 ui_traverse. 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.
ui_traverse is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Iconnect, and thousands of servers like it.
This server
Across the catalogue