Low Risk

get-success-criteria-detail

Gets the normative success criterion requirements - just the title and exception details without Understanding documentation.

How to control get-success-criteria-detail ↓

What get-success-criteria-detail does on WCAG MCP Server

AI agents call get-success-criteria-detail 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-success-criteria-detail needs a policy

This tool purely retrieves and queries structured data from W3C WCAG documentation. It has no side effects, does not modify data, execute operations, or move resources. The read-only nature and informational purpose (accessibility guidelines reference) place it firmly in the Read category with low severity.

From the tool's definition Tool retrieves 'normative success criterion requirements' - specifically 'title and exception details' from WCAG guidelines. No modification, deletion, or execution of code/commands described.

Documented attack patterns abuse exactly the kind of access get-success-criteria-detail gives an agent:

How to control get-success-criteria-detail

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-success-criteria-detail:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-success-criteria-detail": {}
  }
}

get-success-criteria-detail 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-success-criteria-detail

What does the get-success-criteria-detail tool do? +

Gets the normative success criterion requirements - just the title and exception details without Understanding documentation. 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-success-criteria-detail? +

Register the WCAG MCP Server MCP server in PolicyLayer and add a rule for get-success-criteria-detail: 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-success-criteria-detail? +

get-success-criteria-detail is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get-success-criteria-detail? +

Yes. Add a rate_limit block to the get-success-criteria-detail 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-success-criteria-detail completely? +

Set action: deny in the PolicyLayer policy for get-success-criteria-detail. 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-success-criteria-detail? +

get-success-criteria-detail 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.