test_significance · Ai Analyst MCP: Risk & Policy

WHAT IT DOES

What test_significance does on Ai Analyst

AI agents invoke test_significance to trigger actions in Ai Analyst. 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 test_significance needs a policy

The name suggests running a statistical significance test, which involves executing a computation (likely against data). With no description, exact behavior is unknown. Given the server context of 'natural language data queries with statistical rigor,' this is most likely an Execute-category operation (running a statistical test/query). Confidence is lowered due to the empty description.

From the tool's definition Tool name 'test_significance' on a statistical analytics server; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

test_significance Rate-limited

test_significance 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": {
    "test_significance": {
      "limits": [
        {
          "counter": "test_significance_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 Ai Analyst, so you can run agents against it safely.

FAQ

Questions about test_significance

What does the test_significance tool do? +

test_significance. It is categorised as a Execute tool in the Ai Analyst MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on test_significance? +

Register the Ai Analyst MCP server in PolicyLayer and add a rule for test_significance: 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 Ai Analyst. Nothing to install.

What risk level is test_significance? +

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

Can I rate-limit test_significance? +

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

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

test_significance is provided by the Ai Analyst MCP server (sbdk-dev/local-ai-analyst). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.