AI agents call stats_hypothesis to retrieve information from Postgres Mcp Legacy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Hypothesis testing is a statistical analysis operation that reads/queries existing data to compute test statistics and p-values. It performs calculations on data without modifying, deleting, or executing any side-effecting operations. The tool only reads data to perform statistical computations.
From the tool's definition Perform hypothesis testing (t-test, z-test)
Documented attack patterns abuse exactly the kind of access stats_hypothesis gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Postgres Mcp Legacy, and nothing reaches the server without passing your rules. This is the rule we recommend for stats_hypothesis:
{
"version": "1",
"default": "deny",
"tools": {
"stats_hypothesis": {}
}
}stats_hypothesis is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Perform hypothesis testing (t-test, z-test). It is categorised as a Read tool in the Postgres Mcp Legacy MCP Server, which means it retrieves data without modifying state.
Register the Postgres Mcp Legacy MCP server in PolicyLayer and add a rule for stats_hypothesis: 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 Postgres Mcp Legacy. Nothing to install.
stats_hypothesis 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 stats_hypothesis 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 stats_hypothesis. 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.
stats_hypothesis is provided by the Postgres Mcp Legacy MCP server (neverinfamous/postgres-mcp-legacy). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Postgres Mcp Legacy, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
60 Postgres Mcp Legacy tools catalogued and risk-classified — across an index of 43,000+ MCP servers.