ui_accessibility_query
Search for UI elements by accessibility attributes (role, title, value, description, identifier).
This record as markdown: /tools/io-github-heznpc-iconnect/ui-accessibility-query.md
What ui_accessibility_query does on Iconnect
AI agents call ui_accessibility_query 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_accessibility_query is rated Low
This tool retrieves information about UI elements and their accessibility properties. It is a query operation that reads state from the accessibility subsystem without creating, modifying, deleting, or executing actions. While it could theoretically enable surveillance of UI state, the low severity reflects that accessibility queries themselves are informational and passive.
From the tool's definition Tool performs a 'Search' operation for UI elements using accessibility attributes (role, title, value, description, identifier). No modification, deletion, or execution is indicated. The description explicitly states it searches/queries without side effects.
Attacks that exploit this kind of access
The rule that runs ui_accessibility_query 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_accessibility_query, this is the rule to start with:
ui_accessibility_query 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_accessibility_query call is checked against it from then on.
Questions about ui_accessibility_query
Search for UI elements by accessibility attributes (role, title, value, description, identifier). 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_accessibility_query: 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_accessibility_query 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_accessibility_query 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_accessibility_query. 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_accessibility_query 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