AI agents call get-roles-requiring-name to retrieve information from Aria without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward read operation that queries and returns information about ARIA roles and their name requirements. It has no side effects, does not execute code or commands, does not modify data, and does not involve financial transactions.
From the tool's definition Tool name 'get-roles-requiring-name' and description 'List all roles that require an accessible name' indicate a query operation that retrieves information from the W3C WAI-ARIA specification without modifying, executing, or deleting any data.
Attacks that exploit this kind of access
List all roles that require an accessible name. It is categorised as a Read tool in the Aria MCP Server, which means it retrieves data without modifying state.
Register the Aria MCP server in PolicyLayer and add a rule for get-roles-requiring-name: 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 Aria. Nothing to install.
get-roles-requiring-name 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-roles-requiring-name 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-roles-requiring-name. 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-roles-requiring-name is provided by the Aria MCP server (joe-watkins/aria-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →