List all PostgreSQL clusters managed by CloudNativePG.
AI agents call list_postgres_clusters to retrieve information from CloudNativePG MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates existing PostgreSQL clusters without creating, modifying, deleting, or executing operations. It is a pure read operation that poses minimal risk—disclosure of cluster names/metadata is the primary concern, not data corruption or destructive actions.
From the tool's definition Tool name 'list_postgres_clusters' and description 'List all PostgreSQL clusters managed by CloudNativePG' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
List all PostgreSQL clusters managed by CloudNativePG. It is categorised as a Read tool in the CloudNativePG MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CloudNativePG MCP Server MCP server in PolicyLayer and add a rule for list_postgres_clusters: 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 CloudNativePG MCP Server. Nothing to install.
list_postgres_clusters 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 list_postgres_clusters 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 list_postgres_clusters. 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.
list_postgres_clusters is provided by the CloudNativePG MCP Server MCP server (wateim/cnpg-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 →