Get a comprehensive database health report including connection utilization, buffer cache hit ratios, database size, uptime, and transaction throughput. Essential for monitoring production databases.
AI agents call databaseHealth to retrieve information from Postgresql without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
databaseHealth performs monitoring and diagnostic queries only—examining system tables and internal database state to report metrics. It has no side effects, does not modify data, does not execute arbitrary code, and does not delete anything. This is a Read operation.
From the tool's definition The tool description explicitly states it retrieves database health metrics: 'Get a comprehensive database health report including connection utilization, buffer cache hit ratios, database size, uptime, and transaction throughput.' This is pure data retrieval…
Attacks that exploit this kind of access
Get a comprehensive database health report including connection utilization, buffer cache hit ratios, database size, uptime, and transaction throughput. Essential for monitoring production databases. It is categorised as a Read tool in the Postgresql MCP Server, which means it retrieves data without modifying state.
Register the Postgresql MCP server in PolicyLayer and add a rule for databaseHealth: 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. Nothing to install.
databaseHealth 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 databaseHealth 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 databaseHealth. 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.
databaseHealth is provided by the Postgresql MCP server (vnikhilbuddhavarapu/postgresql-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →