thompson_anti_elitism_lint
Scan content for elitism, gatekeeping language, and intellectual intimidation. Deterministic banned-phrase detection + readability scoring. Returns CLEAN or FLAGGED with specific fixes.
This record as markdown: /tools/io-github-homenshum-nodebench/thompson-anti-elitism-lint.md
What thompson_anti_elitism_lint does on Nodebench
AI agents call thompson_anti_elitism_lint to retrieve information from Nodebench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why thompson_anti_elitism_lint is rated Low
This tool performs content analysis and linting — it examines text to identify patterns (elitism, gatekeeping language) and provides feedback. It has no side effects: it does not create, modify, delete, or execute code/commands. It retrieves/queries data (the content being scanned) and returns a read-only report.
From the tool's definition Tool description indicates it 'scans' content and 'returns CLEAN or FLAGGED with specific fixes' — operations that retrieve and analyze data without modifying, deleting, or executing external commands.
Attacks that exploit this kind of access
The rule that runs thompson_anti_elitism_lint safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For thompson_anti_elitism_lint, this is the rule to start with:
thompson_anti_elitism_lint is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every thompson_anti_elitism_lint call is checked against it from then on.
Questions about thompson_anti_elitism_lint
Scan content for elitism, gatekeeping language, and intellectual intimidation. Deterministic banned-phrase detection + readability scoring. Returns CLEAN or FLAGGED with specific fixes. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.
Register the Nodebench MCP server in PolicyLayer and add a rule for thompson_anti_elitism_lint: 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 Nodebench. Nothing to install.
thompson_anti_elitism_lint 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 thompson_anti_elitism_lint 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 thompson_anti_elitism_lint. 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.
thompson_anti_elitism_lint is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue