Get database statistics: size, active connections, cache hit ratio, top tables by size.
AI agents call get_db_stats to retrieve information from PostgreSQL MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries metadata and monitoring information from the database. It has no side effects, does not execute code or commands, does not modify data, and does not delete or overwrite anything. It is purely informational/observational, matching the Read category.
From the tool's definition get_db_stats retrieves database statistics (size, active connections, cache hit ratio, top tables by size) without modifying data or triggering external operations.
Attacks that exploit this kind of access
Get database statistics: size, active connections, cache hit ratio, top tables by size. 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 get_db_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.
get_db_stats 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 get_db_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.
Set action: deny in the PolicyLayer policy for get_db_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.
get_db_stats is provided by the PostgreSQL MCP Server MCP server (sebivarga/mcp_psql_home). 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 →