Remove a table from the database with safety confirmation
AI agents call drop_table to permanently remove resources in DBeaver MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool directly performs an irreversible destructive action—removing an entire table from a database. Even with a 'safety confirmation' mentioned, the core operation cannot be undone and results in total data loss for that table. The blast radius is critical because an AI agent misusing this could permanently destroy production data. This is the most severe category applicable.
From the tool's definition Tool name 'drop_table' combined with description 'Remove a table from the database' explicitly indicates irreversible deletion of database objects. The phrase 'drop table' is standard SQL DDL for permanently deleting tables and their data.
Documented attack patterns abuse exactly the kind of access drop_table 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 drop_table:
{
"version": "1",
"default": "deny",
"hide": [
"drop_table"
]
}drop_table disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove a table from the database with safety confirmation. It is categorised as a Destructive tool in the DBeaver MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the DBeaver MCP Server MCP server in PolicyLayer and add a rule for drop_table: 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.
drop_table is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the drop_table 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 drop_table. 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.
drop_table 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.