quality.evaluate_factuality

Check factual accuracy of responses against knowledge bases

SERVERContextForge MCP Gateway SOURCEjrmatherly/mcp-context-forge

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/jrmatherly-mcp-context-forge/quality.evaluate-factuality.md

WHAT IT DOES

What quality.evaluate_factuality does on ContextForge MCP Gateway

AI agents call quality.evaluate_factuality 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.

RISK

Why quality.evaluate_factuality is rated Low

This tool retrieves or compares data (checking responses against stored knowledge bases) without creating, modifying, executing code, deleting, or moving money. It is fundamentally a read operation that queries knowledge bases for validation purposes. No side effects or state changes are implied.

From the tool's definition Tool name 'evaluate_factuality' combined with description 'Check factual accuracy of responses against knowledge bases' indicates a verification/query operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs quality.evaluate_factuality 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.evaluate_factuality, this is the rule to start with:

quality.evaluate_factuality Allowed

quality.evaluate_factuality is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "quality.evaluate_factuality": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ContextForge MCP Gateway, apply this rule, and every quality.evaluate_factuality call is checked against it from then on.

FAQ

Questions about quality.evaluate_factuality

What does the quality.evaluate_factuality tool do? +

Check factual accuracy of responses against knowledge bases. 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.evaluate_factuality? +

Register the ContextForge MCP Gateway MCP server in PolicyLayer and add a rule for quality.evaluate_factuality: 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.evaluate_factuality? +

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

Can I rate-limit quality.evaluate_factuality? +

Yes. Add a rate_limit block to the quality.evaluate_factuality 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.evaluate_factuality completely? +

Set action: deny in the PolicyLayer policy for quality.evaluate_factuality. 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.evaluate_factuality? +

quality.evaluate_factuality 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.

KEEP EXPLORING

More on ContextForge MCP Gateway, and thousands of servers like it.

This server

All 221 ContextForge MCP Gateway tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →