drop_tables
Drop multiple tables from a database schema
This record as markdown: /tools/cowork-bench/drop-tables.md
What drop_tables does on Cowork Bench
AI agents call drop_tables to permanently remove resources in Cowork Bench, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why drop_tables is rated Critical
This tool performs irreversible deletion of database structures and data. Drop operations cannot be undone without backups and represent permanent data loss. This is the most severe category (Destructive > Execute > Write > Read). The blast radius is critical: an agent misusing this could destroy entire database schemas and lose all data within those tables.
From the tool's definition Tool name is 'drop_tables' and description states 'Drop multiple tables from a database schema'. The verb 'drop' in database contexts is a DDL (Data Definition Language) operation that irreversibly deletes entire tables and all their data.
Attacks that exploit this kind of access
The rule that runs drop_tables safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cowork Bench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For drop_tables, this is the rule to start with:
drop_tables is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Cowork Bench, apply this rule, and every drop_tables call is checked against it from then on.
Questions about drop_tables
Drop multiple tables from a database schema. It is categorised as a Destructive tool in the Cowork Bench MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Cowork Bench MCP server in PolicyLayer and add a rule for drop_tables: 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 Cowork Bench. Nothing to install.
drop_tables 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_tables 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_tables. 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_tables is provided by the Cowork Bench MCP server (0717376/cowork_bench). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cowork Bench, and thousands of servers like it.
Across the catalogue