Gets all success criteria for a specific conformance level. Optionally includes lower levels (e.g., AA includes A).
AI agents call get-criteria-by-level 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 is a straightforward data retrieval tool that queries the WCAG 2.2 guidelines database and returns success criteria matching specified conformance levels (A, AA, AAA). No side effects occur—it does not create, modify, delete, or execute external operations. This is categorized as Read per the classification rules for tools that retrieve or query data without side effects.
From the tool's definition Tool performs a query/retrieval operation: 'Gets all success criteria for a specific conformance level.' Returns WCAG guideline data without modifying, deleting, or executing any operations.
Documented attack patterns abuse exactly the kind of access get-criteria-by-level 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 get-criteria-by-level:
{
"version": "1",
"default": "deny",
"tools": {
"get-criteria-by-level": {}
}
} get-criteria-by-level 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.
Gets all success criteria for a specific conformance level. Optionally includes lower levels (e.g., AA includes A). 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 get-criteria-by-level: 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.
get-criteria-by-level 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-criteria-by-level 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-criteria-by-level. 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-criteria-by-level 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.