Export query results to various formats (CSV, JSON, etc.)
AI agents use export_data 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.
Exporting data creates new files with persistent state changes. While not destructive (the original data remains), and not a direct database modification, it is a write operation that creates artifacts outside the database. The severity is medium because unauthorized exports could leak sensitive data, but the impact is limited to file creation rather than deletion or system execution.
From the tool's definition The tool 'export_data' creates and writes data to new files in formats like CSV and JSON. The description explicitly states it exports query results 'to various formats', which involves file creation/modification.
Documented attack patterns abuse exactly the kind of access export_data 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 export_data:
{
"version": "1",
"default": "deny",
"tools": {
"export_data": {
"limits": [
{
"counter": "export_data_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}export_data 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.
Export query results to various formats (CSV, JSON, etc.). 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 export_data: 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.
export_data 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 export_data 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 export_data. 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.
export_data 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.