AI agents call explain_query 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.
The EXPLAIN PLAN operation is a standard database introspection tool that analyzes query structure and performance characteristics without executing the query against data or causing side effects. It retrieves database schema and optimization information only, making it a Read operation with low severity risk. No data is created, modified, deleted, or financial actions are taken.
From the tool's definition Tool name 'explain_query' and description 'Get the execution plan for a SQL query' indicates a read-only operation that retrieves query metadata without modifying data.
Documented attack patterns abuse exactly the kind of access explain_query 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 explain_query:
{
"version": "1",
"default": "deny",
"tools": {
"explain_query": {}
}
}explain_query 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 the execution plan for a SQL query. 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 explain_query: 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.
explain_query 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 explain_query 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 explain_query. 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.
explain_query 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.