Compare multiple LLM responses to the same prompt and detect inconsistencies using Jaccard word-overlap similarity and fact drift (number comparison). Fast, deterministic, no API key needed. Limitations: relies on surface-level word matching — "Paris is the capital of France" vs "Paris is the Fre...
Part of the Ia Qa Com/mcp llm and RAG testing Dev/QA toolbox server.
Free to start. No card required.
AI agents call consistency_check to retrieve information from Ia Qa Com/mcp llm and RAG testing Dev/QA toolbox without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though consistency_check only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"consistency_check": {}
}
}See the full Ia Qa Com/mcp llm and RAG testing Dev/QA toolbox policy for all 139 tools.
These attack patterns abuse exactly the kind of access consistency_check gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Compare multiple LLM responses to the same prompt and detect inconsistencies using Jaccard word-overlap similarity and fact drift (number comparison). Fast, deterministic, no API key needed. Limitations: relies on surface-level word matching — "Paris is the capital of France" vs "Paris is the French capital" may score low despite semantic equivalence. For true semantic consistency, use run_semantic_tests with embedding mode. Essential for determinism testing.. It is categorised as a Read tool in the Ia Qa Com/mcp llm and RAG testing Dev/QA toolbox MCP Server, which means it retrieves data without modifying state.
Register the Ia Qa Com/mcp llm and RAG testing Dev/QA toolbox MCP server in PolicyLayer and add a rule for consistency_check: 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 Ia Qa Com/mcp llm and RAG testing Dev/QA toolbox. Nothing to install.
consistency_check 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 consistency_check 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 consistency_check. 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.
consistency_check is provided by the Ia Qa Com/mcp llm and RAG testing Dev/QA toolbox MCP server (ia-qa/api). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 139 Ia Qa Com/mcp llm and RAG testing Dev/QA toolbox tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.