List all configured PostgreSQL database connections
AI agents call list_postgresql_connections to retrieve information from MCP Document Converter without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool lists metadata about configured connections without executing queries, modifying data, or triggering side effects. It is a simple informational query operation that falls under the Read category. Severity is low because it only exposes configuration information about existing connections, not actual database data or credentials.
From the tool's definition Tool name 'list_postgresql_connections' and description 'List all configured PostgreSQL database connections' indicate a retrieval/query operation with no modification or execution of code.
Attacks that exploit this kind of access
List all configured PostgreSQL database connections. It is categorised as a Read tool in the MCP Document Converter MCP Server, which means it retrieves data without modifying state.
Register the MCP Document Converter MCP server in PolicyLayer and add a rule for list_postgresql_connections: 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 Document Converter. Nothing to install.
list_postgresql_connections 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_connections 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_connections. 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_connections is provided by the MCP Document Converter MCP server (kittolau/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 →