List all active database connections
AI agents call list_connections to retrieve information from Multi-Database SQL 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 displays metadata about existing database connections. It is informational only—it queries state without side effects, altering no data, executing no code, and deleting nothing. This is a textbook Read operation with minimal blast radius even if misused by an AI agent.
From the tool's definition Tool name 'list_connections' and description 'List all active database connections' indicate a query/retrieval operation with no data modification, deletion, or code execution.
Attacks that exploit this kind of access
List all active database connections. It is categorised as a Read tool in the Multi-Database SQL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Multi-Database SQL MCP Server MCP server in PolicyLayer and add a rule for list_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 Multi-Database SQL MCP Server. Nothing to install.
list_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_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_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_connections is provided by the Multi-Database SQL MCP Server MCP server (soumya7681/sql-mcp-server). 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 →