get_element_roles
Resolve an HTML element (tag + attributes) to the ARIA role(s) it implicitly carries — verbatim from aria-query (ARIA in HTML). Use this when you have markup and want the role, then pass that role to get_aria_role.
This record as markdown: /tools/a11y-assist-mcp/get-element-roles.md
What get_element_roles does on A11y Assist
AI agents call get_element_roles to retrieve information from A11y Assist without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
tag | string | Yes | HTML tag name, e.g. "input", "a", "button", "img". |
attrs | object | — | Attribute values that affect the implicit role, e.g. { "type": "email" } for <input>. |
Parameters from the server's own tool schema.
Why get_element_roles is rated Low
Even though get_element_roles only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs get_element_roles safely
PolicyLayer is an MCP gateway: it sits between your AI agents and A11y Assist, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_element_roles, this is the rule to start with:
get_element_roles 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 A11y Assist, apply this rule, and every get_element_roles call is checked against it from then on.
Questions about get_element_roles
Resolve an HTML element (tag + attributes) to the ARIA role(s) it implicitly carries — verbatim from aria-query (ARIA in HTML). Use this when you have markup and want the role, then pass that role to get_aria_role. It is categorised as a Read tool in the A11y Assist MCP Server, which means it retrieves data without modifying state.
get_element_roles accepts 2 parameters: tag, attrs. Required: tag. The full parameter table on this page comes from the server's own tool schema.
Register the A11y Assist MCP server in PolicyLayer and add a rule for get_element_roles: 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 A11y Assist. Nothing to install.
get_element_roles 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 get_element_roles 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 get_element_roles. 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.
get_element_roles is provided by the A11y Assist MCP server (a11y-assist-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on A11y Assist, and thousands of servers like it.
This server
Across the catalogue