pg_analyze_db_health
Comprehensive database health analysis including cache hit ratio, bloat, replication, and connection stats.
This record as markdown: /tools/io-github-neverinfamous-postgres-mcp/pg-analyze-db-health.md
What pg_analyze_db_health does on PostgreSQL MCP Server
AI agents call pg_analyze_db_health 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_analyze_db_health is rated Low
This tool retrieves and analyzes database health metrics and statistics. It queries system catalogs and performance counters to generate reports on cache performance, table/index bloat, replication status, and connection activity. These are read-only diagnostic operations that produce no side effects on the database state. No data is created, modified, deleted, or destructively changed.
From the tool's definition Tool name 'pg_analyze_db_health' and description indicating it performs 'analysis' of metrics like 'cache hit ratio, bloat, replication, and connection stats' — purely observational/diagnostic operations with no data modification, deletion, or external side…
Attacks that exploit this kind of access
The rule that runs pg_analyze_db_health 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_analyze_db_health, this is the rule to start with:
pg_analyze_db_health is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect PostgreSQL MCP Server, apply this rule, and every pg_analyze_db_health call is checked against it from then on.
Questions about pg_analyze_db_health
Comprehensive database health analysis including cache hit ratio, bloat, replication, and connection stats. It is categorised as a Read tool in the PostgreSQL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PostgreSQL MCP Server MCP server in PolicyLayer and add a rule for pg_analyze_db_health: 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.
pg_analyze_db_health 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 pg_analyze_db_health 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 pg_analyze_db_health. 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.
pg_analyze_db_health 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.
This server
Across the catalogue