AI agents call test_connection 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.
Testing a connection is a read-only diagnostic operation with no side effects on data or system state. It does not retrieve sensitive data at scale, execute queries, modify schemas, delete records, or trigger financial transactions. The blast radius of misuse is minimal - an AI agent could only verify whether a connection works, not cause operational harm through this tool alone.
From the tool's definition Tool description states 'Test connectivity to a database connection' - this is a diagnostic operation that checks whether a connection can be established without modifying, deleting, executing arbitrary operations, or moving money.
Documented attack patterns abuse exactly the kind of access test_connection 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 test_connection:
{
"version": "1",
"default": "deny",
"tools": {
"test_connection": {}
}
}test_connection 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.
Test connectivity to a 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 test_connection: 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.
test_connection 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 test_connection 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 test_connection. 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.
test_connection 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.