Low Risk

get-failures-for-criterion

Gets failure techniques (common mistakes) for a specific success criterion.

How to control get-failures-for-criterion ↓

What get-failures-for-criterion does on WCAG MCP Server

AI agents call get-failures-for-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.

Low Risk

Why get-failures-for-criterion needs a policy

This tool queries and retrieves read-only documentation from the WCAG 2.2 guidelines database. It returns informational content about common accessibility mistakes associated with specific success criteria. There are no side effects, no data modification, no code execution, and no irreversible actions.

From the tool's definition Tool name: 'get-failures-for-criterion'; description indicates retrieval of documentation about 'failure techniques (common mistakes)' for accessibility criteria. No modification, deletion, or execution of external systems occurs.

Documented attack patterns abuse exactly the kind of access get-failures-for-criterion gives an agent:

How to control get-failures-for-criterion

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-failures-for-criterion:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-failures-for-criterion": {}
  }
}

get-failures-for-criterion is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register WCAG MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get-failures-for-criterion

What does the get-failures-for-criterion tool do? +

Gets failure techniques (common mistakes) for a specific success criterion. It is categorised as a Read tool in the WCAG MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-failures-for-criterion? +

Register the WCAG MCP Server MCP server in PolicyLayer and add a rule for get-failures-for-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.

What risk level is get-failures-for-criterion? +

get-failures-for-criterion is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get-failures-for-criterion? +

Yes. Add a rate_limit block to the get-failures-for-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.

How do I block get-failures-for-criterion completely? +

Set action: deny in the PolicyLayer policy for get-failures-for-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.

What MCP server provides get-failures-for-criterion? +

get-failures-for-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.

Enforce policy on every WCAG MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.