AI agents call get-required-context 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 tool queries static ARIA specification data to return role hierarchy information. It is purely informational—retrieving what parent contexts a given role requires for valid ARIA markup. There is no capability to modify ARIA attributes, execute code, delete data, or commit financial actions. The blast radius of misuse is minimal since the tool only provides read-only reference information.
From the tool's definition Tool name 'get-required-context' and description 'Get the required parent context for a role' indicate a retrieval operation that queries the W3C WAI-ARIA specification for parent role requirements. No data modification, execution, or side effects occur.
Attacks that exploit this kind of access
Get the required parent context for a role (e.g., listitem requires list or group). 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-required-context: 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-required-context 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-required-context 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-required-context. 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-required-context 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 →