pg_vacuum_stats

Get detailed vacuum statistics including dead tuples, last vacuum times, and wraparound risk.

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-vacuum-stats.md

WHAT IT DOES

What pg_vacuum_stats does on PostgreSQL MCP Server

AI agents call pg_vacuum_stats 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.

RISK

Why pg_vacuum_stats is rated Low

This is a diagnostic/monitoring tool that reads and returns statistical information about PostgreSQL's vacuum process. It performs no writes, deletes, executions, or financial operations. The verb 'get' and the nature of the data (historical statistics) confirm this is a pure read operation with minimal blast radius.

From the tool's definition Tool retrieves 'detailed vacuum statistics including dead tuples, last vacuum times, and wraparound risk' — a query operation with no modifications or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pg_vacuum_stats safely

PolicyLayer is an MCP gateway: it sits between your AI agents and PostgreSQL MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pg_vacuum_stats, this is the rule to start with:

pg_vacuum_stats Allowed

pg_vacuum_stats 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": {
    "pg_vacuum_stats": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect PostgreSQL MCP Server, apply this rule, and every pg_vacuum_stats call is checked against it from then on.

FAQ

Questions about pg_vacuum_stats

What does the pg_vacuum_stats tool do? +

Get detailed vacuum statistics including dead tuples, last vacuum times, and wraparound risk. 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_vacuum_stats? +

Register the PostgreSQL MCP Server MCP server in PolicyLayer and add a rule for pg_vacuum_stats: 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_vacuum_stats? +

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

Can I rate-limit pg_vacuum_stats? +

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

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

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

KEEP EXPLORING

What pg_vacuum_stats does on PostgreSQL MCP Server

Why pg_vacuum_stats is rated Low

The rule that runs pg_vacuum_stats safely

Questions about pg_vacuum_stats

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