a11y_check
Render UI and report accessibility defects as computed facts with ready-to-apply fixes.
This record as markdown: /tools/a11y-render-gate/a11y-check.md
What a11y_check does on A11y Render Gate
AI agents call a11y_check to retrieve information from A11y Render Gate without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why a11y_check is rated Low
Even though a11y_check 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 a11y_check safely
PolicyLayer is an MCP gateway: it sits between your AI agents and A11y Render Gate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For a11y_check, this is the rule to start with:
a11y_check 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 Render Gate, apply this rule, and every a11y_check call is checked against it from then on.
Questions about a11y_check
Render UI and report accessibility defects as computed facts with ready-to-apply fixes. It is categorised as a Read tool in the A11y Render Gate MCP Server, which means it retrieves data without modifying state.
Register the A11y Render Gate MCP server in PolicyLayer and add a rule for a11y_check: 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 Render Gate. Nothing to install.
a11y_check 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 a11y_check 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 a11y_check. 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.
a11y_check is provided by the A11y Render Gate MCP server (Maher-Reven/a11y-render-gate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on A11y Render Gate, and thousands of servers like it.
This server
Across the catalogue