AI agents call get_categories to retrieve information from Sensitive Lexicon without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about available categories in the sensitive word detection system. It has no side effects, performs no operations, and cannot harm data or trigger external actions. The blast radius of misuse is minimal—an AI agent could only learn what categories exist, which is informational only.
From the tool's definition Tool name 'get_categories' and description 'Get list of available sensitive word categories' indicate a retrieval operation that queries configuration data without modifying, executing, or deleting anything.
Documented attack patterns abuse exactly the kind of access get_categories gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sensitive Lexicon, and nothing reaches the server without passing your rules. This is the rule we recommend for get_categories:
{
"version": "1",
"default": "deny",
"tools": {
"get_categories": {}
}
}get_categories is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get list of available sensitive word categories. It is categorised as a Read tool in the Sensitive Lexicon MCP Server, which means it retrieves data without modifying state.
Register the Sensitive Lexicon 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 Sensitive Lexicon. 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 Sensitive Lexicon MCP server (zephyrpersonal/sensitive-lexicon-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Sensitive Lexicon, 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.
4 Sensitive Lexicon tools catalogued and risk-classified — across an index of 43,000+ MCP servers.