Execute INSERT, UPDATE, or DELETE queries on a specific database connection
AI agents use write_query to create or update resources in DBeaver MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DBeaver MCP Server environment.
The tool modifies data (INSERT/UPDATE) or removes data (DELETE) in databases. INSERT and UPDATE are reversible through transactions or additional queries, placing this in the Write category.
From the tool's definition Tool description explicitly states it executes INSERT, UPDATE, or DELETE queries. INSERT and UPDATE are reversible write operations; DELETE is listed but the tool's primary classification is Write rather than Destructive because the description emphasizes…
Documented attack patterns abuse exactly the kind of access write_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 write_query:
{
"version": "1",
"default": "deny",
"tools": {
"write_query": {
"limits": [
{
"counter": "write_query_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}write_query stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Execute INSERT, UPDATE, or DELETE queries on a specific database connection. It is categorised as a Write tool in the DBeaver MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DBeaver MCP Server MCP server in PolicyLayer and add a rule for write_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.
write_query is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the write_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 write_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.
write_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.