ui_accessibility_query

Search for UI elements by accessibility attributes (role, title, value, description, identifier).

SERVERAirMCP SOURCEairmcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/heznpc-airmcp/ui-accessibility-query.md

WHAT IT DOES

What ui_accessibility_query does on AirMCP

AI agents call ui_accessibility_query to retrieve information from AirMCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why ui_accessibility_query is rated Low

The tool performs information retrieval on accessibility attributes (role, title, value, description, identifier) of UI elements. No side effects, no state changes, no code execution, and no data modification occur. This is a read-only introspection capability similar to inspecting DOM or UI hierarchies. Confidence is high because the description is explicit and unambiguous.

From the tool's definition Tool description states 'Search for UI elements by accessibility attributes' — this is a query/search operation with no modification, deletion, or execution of commands. It retrieves metadata about UI structure only.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ui_accessibility_query safely

PolicyLayer is an MCP gateway: it sits between your AI agents and AirMCP, 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 Allowed

ui_accessibility_query is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ui_accessibility_query": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect AirMCP, apply this rule, and every ui_accessibility_query call is checked against it from then on.

FAQ

Questions about ui_accessibility_query

What does the ui_accessibility_query tool do? +

Search for UI elements by accessibility attributes (role, title, value, description, identifier). It is categorised as a Read tool in the AirMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ui_accessibility_query? +

Register the Air 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 AirMCP. Nothing to install.

What risk level is ui_accessibility_query? +

ui_accessibility_query is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit ui_accessibility_query? +

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.

How do I block ui_accessibility_query completely? +

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.

What MCP server provides ui_accessibility_query? +

ui_accessibility_query is provided by the Air MCP server (airmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Air, and thousands of servers like it.

This server

All 279 Air tools →

Across the catalogue

claude_query on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →