Execute a SQL query on a specific database connection (read-only queries)
AI agents invoke execute_query to trigger actions in DBeaver MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The Execute category is appropriate because this tool runs SQL queries whose effects depend on the query argument and database state. Although the description claims 'read-only', SQL execution is inherently an Execute operation—it triggers external database operations whose outcome depends on the query content.
From the tool's definition Tool description states 'Execute a SQL query' and name is 'execute_query'. Despite the qualifier '(read-only queries)', the tool executes arbitrary SQL queries which can have side effects depending on the database connection and query content.
Documented attack patterns abuse exactly the kind of access execute_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 execute_query:
{
"version": "1",
"default": "deny",
"tools": {
"execute_query": {
"limits": [
{
"counter": "execute_query_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}execute_query stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Execute a SQL query on a specific database connection (read-only queries). It is categorised as a Execute tool in the DBeaver MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the DBeaver MCP Server MCP server in PolicyLayer and add a rule for execute_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.
execute_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the execute_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 execute_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.
execute_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.