Low Risk

search-glossary

Searches the WCAG glossary by keyword.

How to control search-glossary ↓

What search-glossary does on WCAG MCP Server

AI agents call search-glossary 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 search-glossary needs a policy

This tool only retrieves and queries existing WCAG glossary data. It performs no writes, deletions, code execution, or financial operations. The search operation is read-only with no capability to modify the underlying glossary database or trigger external actions. Blast radius is minimal — worst case is returning incorrect or misleading accessibility guidance information.

From the tool's definition Tool is described as 'Searches the WCAG glossary by keyword' — a pure search/query operation that retrieves glossary term data without modification or side effects.

Documented attack patterns abuse exactly the kind of access search-glossary gives an agent:

How to control search-glossary

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 search-glossary:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search-glossary": {}
  }
}

search-glossary 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 search-glossary

What does the search-glossary tool do? +

Searches the WCAG glossary by keyword. 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 search-glossary? +

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

search-glossary is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search-glossary? +

Yes. Add a rate_limit block to the search-glossary 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 search-glossary completely? +

Set action: deny in the PolicyLayer policy for search-glossary. 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 search-glossary? +

search-glossary 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.