prompt.test_consistency

Test prompt consistency across multiple runs and temperature settings

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/prompt.test-consistency.md

WHAT IT DOES

What prompt.test_consistency does on ContextForge MCP Gateway

AI agents call prompt.test_consistency 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 prompt.test_consistency is rated Low

This tool reads/evaluates prompt behavior across conditions (multiple runs, temperature settings) and reports results. It performs introspection and diagnostics without side effects.

From the tool's definition Tool description explicitly states it 'test[s] prompt consistency' — a diagnostic/analytical operation that queries or evaluates behavior without modifying, deleting, or executing external code.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

prompt.test_consistency Allowed

prompt.test_consistency 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": {
    "prompt.test_consistency": {}
  }
}

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 prompt.test_consistency call is checked against it from then on.

FAQ

Questions about prompt.test_consistency

What does the prompt.test_consistency tool do? +

Test prompt consistency across multiple runs and temperature settings. 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 prompt.test_consistency? +

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

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

Can I rate-limit prompt.test_consistency? +

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

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

prompt.test_consistency 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 →