# a11y_explain

Get the complete detail for one finding id from the last a11y_check run: every measured

Agent View of the PolicyLayer registry record for `a11y_explain`. HTML page: https://policylayer.com/tools/a11y-render-gate/a11y-explain

## Facts

- Tool: `a11y_explain`
- Server: A11y Render Gate (`Maher-Reven/a11y-render-gate`) — https://policylayer.com/tools/a11y-render-gate.md
- Homepage: https://github.com/Maher-Reven/a11y-render-gate
- Risk category: Execute (High risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "a11y_explain",
    "arguments": {}
  }
}
```

## Why a11y_explain is rated High

a11y_explain triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Risk signals: Bulk/mass operation — affects multiple targets

## Use case

AI agents invoke a11y_explain to trigger actions in A11y Render Gate. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches A11y Render Gate:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "a11y_explain": {
      "limits": [
        {
          "counter": "a11y_explain_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on A11y Render Gate (3)

- `a11y_accept_baseline` — Read — https://policylayer.com/tools/a11y-render-gate/a11y-accept-baseline.md
- `a11y_check` — Read — https://policylayer.com/tools/a11y-render-gate/a11y-check.md
- `a11y_status` — Read — https://policylayer.com/tools/a11y-render-gate/a11y-status.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=a11y-render-gate · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/a11y-render-gate