statistical_test · ContextForge MCP Gateway MCP

WHAT IT DOES

What statistical_test does on ContextForge MCP Gateway

AI agents invoke statistical_test to trigger actions in ContextForge MCP Gateway. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why statistical_test needs a policy

This tool executes a statistical algorithm (hypothesis testing) against provided data. It does not merely retrieve stored data but actively computes results, placing it in the Execute category. Misuse risk is medium since it processes data and could return misleading results if misused, but has no direct destructive or financial impact.

From the tool's definition 'Perform statistical hypothesis testing' — actively runs a statistical computation/test on input data

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

statistical_test Rate-limited

statistical_test stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "statistical_test": {
      "limits": [
        {
          "counter": "statistical_test_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ContextForge MCP Gateway, so you can run agents against it safely.

FAQ

Questions about statistical_test

What does the statistical_test tool do? +

Perform statistical hypothesis testing. It is categorised as a Execute tool in the ContextForge MCP Gateway MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on statistical_test? +

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

statistical_test is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit statistical_test? +

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

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

statistical_test 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.