search_wcag
Search WCAG Success Criteria by keyword, gated to a conformance level. Returns id / level / title. Use get_wcag_sc for the full SC with techniques and failures. (Most drill-down flows reach SCs via search_act; use this for direct keyword lookups.)
This record as markdown: /tools/a11y-assist-mcp/search-wcag.md
What search_wcag does on A11y Assist
AI agents call search_wcag to retrieve information from A11y Assist without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
level | string | — | Conformance level (cumulative): AA keeps A + AA, AAA keeps all. |
query | string | Yes | Term to match against SC id, title, and statement, e.g. "focus", "contrast", "name". |
Parameters from the server's own tool schema.
Why search_wcag is rated Low
Even though search_wcag only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs search_wcag safely
PolicyLayer is an MCP gateway: it sits between your AI agents and A11y Assist, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_wcag, this is the rule to start with:
search_wcag is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect A11y Assist, apply this rule, and every search_wcag call is checked against it from then on.
Questions about search_wcag
Search WCAG Success Criteria by keyword, gated to a conformance level. Returns id / level / title. Use get_wcag_sc for the full SC with techniques and failures. (Most drill-down flows reach SCs via search_act; use this for direct keyword lookups.). It is categorised as a Read tool in the A11y Assist MCP Server, which means it retrieves data without modifying state.
search_wcag accepts 2 parameters: level, query. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the A11y Assist 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 A11y Assist. 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 A11y Assist MCP server (a11y-assist-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on A11y Assist, and thousands of servers like it.
This server
Across the catalogue