Detect sensitive words in text using the Sensitive-lexicon library
AI agents call detect_sensitive_words 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 scans text against a lexicon to identify sensitive words and reports findings. It retrieves/analyzes information with no side effects, reversible changes, code execution, data destruction, or financial impact. The capability is similar to search or query operations that analyze content without altering it.
From the tool's definition Tool performs detection and analysis of text ('Detect sensitive words in text') without modifying, deleting, or executing external operations. Returns results about sensitive content found.
Documented attack patterns abuse exactly the kind of access detect_sensitive_words 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 detect_sensitive_words:
{
"version": "1",
"default": "deny",
"tools": {
"detect_sensitive_words": {}
}
}detect_sensitive_words 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.
Detect sensitive words in text using the Sensitive-lexicon library. 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 detect_sensitive_words: 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.
detect_sensitive_words 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 detect_sensitive_words 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 detect_sensitive_words. 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.
detect_sensitive_words 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.