get_wcag_sc
Return a WCAG 2.2 Success Criterion in full: its verbatim statement plus its sufficient techniques and documented failures (the W3C-published anti-patterns). Explicit by-id fetch — not level-gated.
This record as markdown: /tools/a11y-assist-mcp/get-wcag-sc.md
What get_wcag_sc does on A11y Assist
AI agents call get_wcag_sc 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 |
|---|---|---|---|
id | string | Yes | WCAG 2.2 Success Criterion id, e.g. "4.1.2". From a search_act / search_wcag result. |
Parameters from the server's own tool schema.
Why get_wcag_sc is rated Low
Even though get_wcag_sc 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 get_wcag_sc 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 get_wcag_sc, this is the rule to start with:
get_wcag_sc 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 get_wcag_sc call is checked against it from then on.
Questions about get_wcag_sc
Return a WCAG 2.2 Success Criterion in full: its verbatim statement plus its sufficient techniques and documented failures (the W3C-published anti-patterns). Explicit by-id fetch — not level-gated. It is categorised as a Read tool in the A11y Assist MCP Server, which means it retrieves data without modifying state.
get_wcag_sc accepts 1 parameter: id. Required: id. 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 get_wcag_sc: 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.
get_wcag_sc 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_wcag_sc 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_wcag_sc. 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_wcag_sc 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