List every privacy-tool category in the directory with a tool count per category. Parent categories include child-category tools in their count. When to call: BEFORE search_privacy_tools when the user has not specified a category slug — agents need valid slugs to pass as the category filter. Also...
Risk signalsBulk/mass operation — affects multiple targets
Part of the Default Privacy server.
Free to start. No card required.
AI agents call get_categories 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 get_categories 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": {
"get_categories": {}
}
}See the full Default Privacy policy for all 33 tools.
These attack patterns abuse exactly the kind of access get_categories 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.
List every privacy-tool category in the directory with a tool count per category. Parent categories include child-category tools in their count. When to call: BEFORE search_privacy_tools when the user has not specified a category slug — agents need valid slugs to pass as the category filter. Also useful when the user asks "what categories exist" or "what kinds of privacy tools do you index". PREFER search_privacy_tools if the user has already named a topic; categories are a discovery aid, not the answer surface. Input Requirements: - include_empty is OPTIONAL (default false). Set true to also return categories that currently have zero published tools. Output: { categories: [{ slug, name, description, parent_id, tool_count }], total, usage_hint, citation }. usage_hint explains how to feed a slug back into search_privacy_tools. PREFER citing the citation URL when the user wants to browse the categories directly.. 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 get_categories: 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.
get_categories 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 get_categories 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 get_categories. 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.
get_categories 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.