Explain an axe-core accessibility rule — what WCAG criteria it maps to, what it means, and how to fix it. Use this to understand a specific violation without running a scan.
AI agents call explain_violation to retrieve information from aria51 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool is a lookup/retrieval function that returns reference data about WCAG violations and remediation guidance. It does not scan, execute code, modify data, trigger external operations, or delete anything. It is purely informational, analogous to querying a documentation database.
From the tool's definition Tool 'explain_violation' retrieves and returns explanatory information about accessibility rules — 'what WCAG criteria it maps to, what it means, and how to fix it' — with no modification, deletion, or execution of external systems.
Attacks that exploit this kind of access
Explain an axe-core accessibility rule — what WCAG criteria it maps to, what it means, and how to fix it. Use this to understand a specific violation without running a scan. It is categorised as a Read tool in the aria51 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the aria51 MCP Server MCP server in PolicyLayer and add a rule for explain_violation: 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 aria51 MCP Server. Nothing to install.
explain_violation 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 explain_violation 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 explain_violation. 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.
explain_violation is provided by the aria51 MCP Server MCP server (justinleeirizarry/aria51). 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 →