list_postgresql_connection_pools
List all connection pools for a PostgreSQL database instance
This record as markdown: /tools/takashito-linode-mcp-server/list-postgresql-connection-pools.md
What list_postgresql_connection_pools does on Linode MCP Server
AI agents call list_postgresql_connection_pools to retrieve information from Linode MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_postgresql_connection_pools is rated Low
This tool queries and returns information about existing PostgreSQL connection pools. It performs a read-only operation that retrieves data without creating, modifying, deleting, or executing any changes to infrastructure or data. The blast radius is minimal as misuse would only expose configuration details already owned by the authenticated user.
From the tool's definition Tool name is 'list_postgresql_connection_pools' and description states 'List all connection pools for a PostgreSQL database instance' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs list_postgresql_connection_pools safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Linode MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_postgresql_connection_pools, this is the rule to start with:
list_postgresql_connection_pools is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Linode MCP Server, apply this rule, and every list_postgresql_connection_pools call is checked against it from then on.
Questions about list_postgresql_connection_pools
List all connection pools for a PostgreSQL database instance. It is categorised as a Read tool in the Linode MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Linode MCP Server MCP server in PolicyLayer and add a rule for list_postgresql_connection_pools: 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 Linode MCP Server. Nothing to install.
list_postgresql_connection_pools 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_postgresql_connection_pools 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_postgresql_connection_pools. 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_postgresql_connection_pools is provided by the Linode MCP Server MCP server (takashito/linode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Linode MCP Server, and thousands of servers like it.
This server
Across the catalogue