get-techniques-for-criterion

THE RISK

Low Risk

Why get-techniques-for-criterion needs a policy

This tool retrieves and returns documentation about WCAG techniques and success criteria—pure information lookup with no side effects, modifications, deletions, code execution, or financial impact. It fits the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).'

From the tool's definition Tool name 'get-techniques-for-criterion' and description 'Gets all techniques' indicate a retrieval operation. No write, delete, execute, or financial operations are performed.

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

POLICY

How to control get-techniques-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-techniques-for-criterion:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-techniques-for-criterion": {}
  }
}

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

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

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More WCAG MCP Server tools

Read whats-new-in-wcag22 Lists all success criteria that were added in WCAG 2.2. Read count-criteria Returns counts of success criteria grouped by level, principle, or guideline. Read get-criteria-by-level Gets all success criteria for a specific conformance level. Optionally includes lower leve Read get-criterion Gets full details for a specific WCAG success criterion by its reference number (e.g., Read get-failures-for-criterion Gets failure techniques (common mistakes) for a specific success criterion. Read get-full-criterion-context Gets comprehensive context for a success criterion including techniques, test rules, and r Read get-glossary-term Gets the definition of a WCAG glossary term. Read get-guideline Gets full details for a specific WCAG guideline including all its success criteria.

All 20 WCAG MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get-techniques-for-criterion

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

Gets all techniques (sufficient, advisory, and failures) 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-techniques-for-criterion? +

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

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

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

Yes. Add a rate_limit block to the get-techniques-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-techniques-for-criterion completely? +

Set action: deny in the PolicyLayer policy for get-techniques-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-techniques-for-criterion? +

get-techniques-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.

CHECK YOUR STACK →