Lists WCAG 2.2 guidelines, optionally filtered by principle number (1-4).
AI agents call list-guidelines 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 retrieves and presents existing WCAG guideline data without creating, modifying, deleting, executing commands, or affecting any resources. It is a straightforward informational query against a static documentation database. The optional filter parameter does not change the fundamental read-only nature of the operation.
From the tool's definition Tool description states it 'Lists WCAG 2.2 guidelines' with optional filtering. The verb 'lists' and the read-only nature of querying structured accessibility documentation confirms this is a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access list-guidelines 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-guidelines:
{
"version": "1",
"default": "deny",
"tools": {
"list-guidelines": {}
}
}list-guidelines 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 guidelines, optionally filtered by principle number (1-4). 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-guidelines: 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-guidelines 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-guidelines 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-guidelines. 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-guidelines 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.