quality.assess_toxicity
Detect harmful or biased content using pattern matching and LLM analysis
This record as markdown: /tools/jrmatherly-mcp-context-forge/quality.assess-toxicity.md
What quality.assess_toxicity does on ContextForge MCP Gateway
AI agents call quality.assess_toxicity to retrieve information from ContextForge MCP Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why quality.assess_toxicity is rated Low
This is a Read operation. It analyzes content to identify toxicity or bias but does not mutate data, execute code, delete resources, or move funds. The tool retrieves or classifies information about harmful content without side effects. Severity is low because misuse (e.g., an agent over-reporting content as toxic) has no destructive consequences; it merely produces analysis output.
From the tool's definition Tool performs content analysis and detection without modification—'Detect harmful or biased content using pattern matching and LLM analysis' describes observation and classification only, not creation, modification, deletion, or execution of external…
Attacks that exploit this kind of access
The rule that runs quality.assess_toxicity safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ContextForge MCP Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For quality.assess_toxicity, this is the rule to start with:
quality.assess_toxicity 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 ContextForge MCP Gateway, apply this rule, and every quality.assess_toxicity call is checked against it from then on.
Questions about quality.assess_toxicity
Detect harmful or biased content using pattern matching and LLM analysis. It is categorised as a Read tool in the ContextForge MCP Gateway MCP Server, which means it retrieves data without modifying state.
Register the ContextForge MCP Gateway MCP server in PolicyLayer and add a rule for quality.assess_toxicity: 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 ContextForge MCP Gateway. Nothing to install.
quality.assess_toxicity 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 quality.assess_toxicity 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 quality.assess_toxicity. 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.
quality.assess_toxicity is provided by the ContextForge MCP Gateway MCP server (jrmatherly/mcp-context-forge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ContextForge MCP Gateway, and thousands of servers like it.
This server
Across the catalogue