Return the list of configured database connections (name and type only — no passwords).
AI agents call get_connections to retrieve information from MCP Database Query Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only lists metadata about configured connections without exposing credentials or modifying any data. It is a simple information retrieval operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool returns 'the list of configured database connections (name and type only)' — a pure retrieval operation with no side effects. Server explicitly describes itself as 'read-only workflow.'
Attacks that exploit this kind of access
Return the list of configured database connections (name and type only — no passwords). It is categorised as a Read tool in the MCP Database Query Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Database Query Server MCP server in PolicyLayer and add a rule for get_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 Query Server. Nothing to install.
get_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 get_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 get_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.
get_connections is provided by the MCP Database Query Server MCP server (vicus-brits/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 →