quality.assess_toxicity

Detect harmful or biased content using pattern matching and LLM analysis

Server ContextForge MCP Gateway jrmatherly/mcp-context-forge
Category Read
Risk class Low
Parameters 00 required

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 — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why quality.assess_toxicity needs a policy

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…

Questions about quality.assess_toxicity

What does the quality.assess_toxicity tool do? +

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.

How do I enforce a policy on quality.assess_toxicity? +

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.

What risk level is quality.assess_toxicity? +

quality.assess_toxicity is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit quality.assess_toxicity? +

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.

How do I block quality.assess_toxicity completely? +

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.

What MCP server provides quality.assess_toxicity? +

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.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.