Get detailed information about a specific database connection
AI agents call get_connection_info to retrieve information from DBeaver 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 connection details (credentials, host, port, authentication info, etc.) but does not modify data or execute operations. However, the sensitivity of connection information—which may include credentials or secrets—elevates severity from low to medium, as exposure could enable unauthorized database access. The tool itself performs only a read operation with no side effects.
From the tool's definition Tool name 'get_connection_info' and description 'Get detailed information about a specific database connection' indicates retrieval of connection metadata without modification.
Documented attack patterns abuse exactly the kind of access get_connection_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DBeaver MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_connection_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_connection_info": {}
}
}get_connection_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get detailed information about a specific database connection. It is categorised as a Read tool in the DBeaver MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DBeaver MCP Server MCP server in PolicyLayer and add a rule for get_connection_info: 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 DBeaver MCP Server. Nothing to install.
get_connection_info 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_connection_info 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_connection_info. 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_connection_info is provided by the DBeaver MCP Server MCP server (srthkdev/omnisql-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 21 DBeaver MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
21 DBeaver MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.