Search Default Privacy's glossary of privacy + LLC terminology. Glossary entries are short, definitional, and cross-reference each other plus relevant guides. When to call: when the user asks "what is X" / "what does Y mean" / "define Z" — anything that wants a definition rather than a how-to. PR...
Risk signalsAccepts freeform code/query input (query)
Part of the Default Privacy server.
Free to start. No card required.
AI agents call search_glossary to retrieve information from Default Privacy without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though search_glossary only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"search_glossary": {}
}
}See the full Default Privacy policy for all 33 tools.
These attack patterns abuse exactly the kind of access search_glossary gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Search Default Privacy's glossary of privacy + LLC terminology. Glossary entries are short, definitional, and cross-reference each other plus relevant guides. When to call: when the user asks "what is X" / "what does Y mean" / "define Z" — anything that wants a definition rather than a how-to. PREFER search_guides for procedural / explanatory content. Input Requirements: - At least ONE of query or category SHOULD be passed; an empty call returns a generic discovery error. - limit is OPTIONAL (default 12, max 50). Output: matching glossary entries, each with slug, term, short_definition, category, url (MCP-attribution-tagged), and aliases. Empty results carry broadening suggestions. PREFER quoting the url values verbatim and following up with get_glossary_term(slug) when the user wants the long definition + related concepts.. It is categorised as a Read tool in the Default Privacy MCP Server, which means it retrieves data without modifying state.
Register the Default Privacy 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 Default Privacy. Nothing to install.
search_glossary 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 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.
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.
search_glossary is provided by the Default Privacy MCP server (https://defaultprivacy.com/api/privacy/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 33 Default Privacy tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.