Lists WCAG 2.2 success criteria with optional filters by level (A, AA, AAA), guideline (e.g.,
AI agents call list-success-criteria to retrieve information from WCAG MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves accessibility guideline information from a static W3C data source. It performs filtering and listing operations only, with no side effects, data modification, code execution, or resource consumption beyond read access. The blast radius of misuse is minimal—an agent could retrieve information it shouldn't see, but cannot alter guidelines, execute code, or cause harm.
From the tool's definition Tool name 'list-success-criteria' and description indicate it 'Lists WCAG 2.2 success criteria with optional filters' - a pure data retrieval operation with no modification, deletion, or execution capabilities.
Documented attack patterns abuse exactly the kind of access list-success-criteria gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WCAG MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list-success-criteria:
{
"version": "1",
"default": "deny",
"tools": {
"list-success-criteria": {}
}
} list-success-criteria is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Lists WCAG 2.2 success criteria with optional filters by level (A, AA, AAA), guideline (e.g.,. It is categorised as a Read tool in the WCAG MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WCAG MCP Server MCP server in PolicyLayer and add a rule for list-success-criteria: 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 WCAG MCP Server. Nothing to install.
list-success-criteria 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 list-success-criteria 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 list-success-criteria. 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.
list-success-criteria is provided by the WCAG MCP Server MCP server (joe-watkins/wcag-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from WCAG MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 WCAG MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.