Get connection status and server event history
AI agents call status to retrieve information from Fluid Postgres without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns metadata about the current database connection and historical server events. It performs no writes, deletes, code execution, or financial operations—it is purely informational, similar to checking server health metrics. The low severity reflects that misuse would only expose status information without capability to harm data or systems.
From the tool's definition Tool name 'status' and description 'Get connection status and server event history' indicate retrieval of diagnostic information with no side effects or data modifications.
Attacks that exploit this kind of access
Get connection status and server event history. It is categorised as a Read tool in the Fluid Postgres MCP Server, which means it retrieves data without modifying state.
Register the Fluid Postgres MCP server in PolicyLayer and add a rule for 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 Fluid Postgres. Nothing to install.
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 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 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.
status is provided by the Fluid Postgres MCP server (povesma/fluid-postgres-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 →