Searches WCAG 2.2 success criteria by keyword in titles and descriptions.
AI agents call search-wcag 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 queries data from a static WCAG guidelines database without any side effects. It matches the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).' The search operation cannot modify, delete, or execute code. Even if an AI agent misuses it, the worst outcome is retrieving irrelevant accessibility documentation, posing minimal security risk.
From the tool's definition Tool searches WCAG success criteria by keyword in titles and descriptions. No modification, deletion, execution, or financial operations are performed. The description explicitly indicates a retrieval/query operation ('searches...by keyword').
Documented attack patterns abuse exactly the kind of access search-wcag 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 search-wcag:
{
"version": "1",
"default": "deny",
"tools": {
"search-wcag": {}
}
} search-wcag 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.
Searches WCAG 2.2 success criteria by keyword in titles and descriptions. 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 search-wcag: 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.
search-wcag 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 search-wcag 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 search-wcag. 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.
search-wcag 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.