List configured database connections and their permission (readonly).
AI agents call list_connections to retrieve information from MCP Database Manager without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns information about existing database connections and their associated permissions. It performs no creation, modification, deletion, or execution of operations. The impact of misuse is limited to information disclosure about connection configuration, which represents a low severity risk. The tool clearly falls under the Read category as it retrieves data without side effects.
From the tool's definition The tool 'list_connections' with description 'List configured database connections and their permission (readonly)' retrieves connection configuration information without modification.
Attacks that exploit this kind of access
List configured database connections and their permission (readonly). It is categorised as a Read tool in the MCP Database Manager MCP Server, which means it retrieves data without modifying state.
Register the MCP Database Manager 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 MCP Database Manager. 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 MCP Database Manager MCP server (meimingqi222/mcp-database-manager). 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 →