Get database connection status and performance metrics
AI agents call get_connection_status to retrieve information from MCP PostgreSQL Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves connection and performance metadata from the database. It has no side effects, does not modify data, and does not execute arbitrary code. It is a read-only diagnostic operation. The server's stated purpose is 'secure read-only access', and this tool aligns with that constraint. Severity is low because misuse would only expose system metadata, not sensitive data or cause operational harm.
From the tool's definition Tool name 'get_connection_status' and description 'Get database connection status and performance metrics' indicate a query operation that retrieves status information without modifying data or executing commands.
Attacks that exploit this kind of access
Get database connection status and performance metrics. It is categorised as a Read tool in the MCP PostgreSQL Server MCP Server, which means it retrieves data without modifying state.
Register the MCP PostgreSQL Server MCP server in PolicyLayer and add a rule for get_connection_status: 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 MCP PostgreSQL Server. Nothing to install.
get_connection_status 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_connection_status 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_connection_status. 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_connection_status is provided by the MCP PostgreSQL Server MCP server (kristofer84/mcp-postgres). 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 →