Remove all data from a table while preserving its schema.
AI agents call clear_table to permanently remove resources in Dune — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes all rows from a table without the ability to undo the action. While the schema is preserved (making it technically less severe than DROP TABLE), the complete data loss is irreversible and represents a destructive operation.
From the tool's definition Tool name 'clear_table' and description 'Remove all data from a table while preserving its schema' indicate irreversible deletion of all table contents. The verb 'remove' combined with 'all data' demonstrates destructive capability.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Remove all data from a table while preserving its schema. It is categorised as a Destructive tool in the Dune MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Dune MCP server in PolicyLayer and add a rule for clear_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 Dune. Nothing to install.
clear_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 clear_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 clear_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.
clear_table is provided by the Dune MCP server (mwamedacen/dune-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →