Get connection pool statistics for a connection
AI agents call get_pool_stats 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 pool statistics, which is a read-only operation that returns metadata about database connection status. It does not create, modify, delete, execute, or transfer data. The information returned is diagnostic/operational metadata used for monitoring database connections. No data is at risk of being modified or lost through this operation.
From the tool's definition Tool name 'get_pool_stats' and description 'Get connection pool statistics for a connection' indicate retrieval of monitoring/diagnostic data without modification or side effects.
Documented attack patterns abuse exactly the kind of access get_pool_stats 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_pool_stats:
{
"version": "1",
"default": "deny",
"tools": {
"get_pool_stats": {}
}
}get_pool_stats 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 connection pool statistics for a 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_pool_stats: 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_pool_stats 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_pool_stats 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_pool_stats. 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_pool_stats 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.