AI agents call analyze_db_health to retrieve information from Pgsql without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs health checks and analysis, which are read-only operations that query database state and return diagnostic information. It does not modify data, execute arbitrary code, delete data, or perform financial transactions. The server's description mentions 'configurable read-only mode for production use', further indicating this tool operates safely without side effects.
From the tool's definition Tool name is 'analyze_db_health' and description indicates it 'Analyzes database health' with 'available health checks'. The verb 'analyze' and 'checks' indicate diagnostic/monitoring operations that retrieve data without modification.
Attacks that exploit this kind of access
Analyzes database health. Here are the available health checks:\n. It is categorised as a Read tool in the Pgsql MCP Server, which means it retrieves data without modifying state.
Register the Pgsql MCP server in PolicyLayer and add a rule for 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 Pgsql. Nothing to install.
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 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 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.
analyze_db_health is provided by the Pgsql MCP server (surajmandalcell/pgsql-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 →