pg_stats_hypothesis

Perform one-sample t-test or z-test against a hypothesized mean. For z-test, provide populationStdDev (sigma) for accurate results. Use groupBy to test each group separately.

SERVERPostgreSQL MCP Server SOURCE@neverinfamous/postgres-mcp
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/io-github-neverinfamous-postgres-mcp/pg-stats-hypothesis.md

What pg_stats_hypothesis does on PostgreSQL MCP Server

AI agents call pg_stats_hypothesis to retrieve information from PostgreSQL MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why pg_stats_hypothesis is rated Low

This tool retrieves and analyzes statistical data to test hypotheses. It computes test statistics and results but does not create, modify, delete, or execute external operations. The optional groupBy parameter allows segmentation of analysis but remains a read operation. No side effects or data mutation occurs.

From the tool's definition Tool performs statistical hypothesis testing (t-test/z-test) on data; 'Perform one-sample t-test or z-test against a hypothesized mean' indicates read-only data analysis without modification or execution of arbitrary code.

Questions about pg_stats_hypothesis

What does the pg_stats_hypothesis tool do? +

Perform one-sample t-test or z-test against a hypothesized mean. For z-test, provide populationStdDev (sigma) for accurate results. Use groupBy to test each group separately. It is categorised as a Read tool in the PostgreSQL MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on pg_stats_hypothesis? +

Register the PostgreSQL MCP Server MCP server in PolicyLayer and add a rule for pg_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 PostgreSQL MCP Server. Nothing to install.

What risk level is pg_stats_hypothesis? +

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

Can I rate-limit pg_stats_hypothesis? +

Yes. Add a rate_limit block to the pg_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.

How do I block pg_stats_hypothesis completely? +

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

What MCP server provides pg_stats_hypothesis? +

pg_stats_hypothesis is provided by the PostgreSQL MCP Server MCP server (@neverinfamous/postgres-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on PostgreSQL MCP Server, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of PostgreSQL MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.