Gets full details for a specific WCAG success criterion by its reference number (e.g.,
AI agents call get-criterion 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 performs a straightforward data retrieval operation against a static knowledge base of accessibility guidelines. It has no side effects, cannot modify data, execute code, or cause any impact beyond returning read-only reference information. The blast radius of misuse is minimal - an AI agent could only retrieve already-public WCAG documentation. Classification as Read is appropriate.
From the tool's definition Tool name 'get-criterion' and description indicate it 'Gets full details for a specific WCAG success criterion' - a retrieval operation that queries and returns WCAG accessibility guideline documentation without modifying, executing, or deleting any data.
Documented attack patterns abuse exactly the kind of access get-criterion 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-criterion:
{
"version": "1",
"default": "deny",
"tools": {
"get-criterion": {}
}
} get-criterion 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 full details for a specific WCAG success criterion by its reference number (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 get-criterion: 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-criterion 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-criterion 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-criterion. 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-criterion 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.