Deletes a dataset from Superset. This is a permanent operation and cannot be undone. Be cautious, as deleting a dataset will also break any charts and dashboards that depend on it.
AI agents call delete_dataset to permanently remove resources in Superset — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool irreversibly deletes data (a dataset) and causes cascading damage to dependent objects (charts and dashboards). The description explicitly emphasizes permanence and inability to undo, which is the hallmark of Destructive category.
From the tool's definition Tool description explicitly states: 'Deletes a dataset from Superset. This is a permanent operation and cannot be undone.' and warns that 'deleting a dataset will also break any charts and dashboards that depend on it.'
Documented attack patterns abuse exactly the kind of access delete_dataset gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Superset, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_dataset:
{
"version": "1",
"default": "deny",
"hide": [
"delete_dataset"
]
} delete_dataset 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.
Deletes a dataset from Superset. This is a permanent operation and cannot be undone. Be cautious, as deleting a dataset will also break any charts and dashboards that depend on it. It is categorised as a Destructive tool in the Superset MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Superset MCP server in PolicyLayer and add a rule for delete_dataset: 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 Superset. Nothing to install.
delete_dataset 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 delete_dataset 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 delete_dataset. 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.
delete_dataset is provided by the Superset MCP server (winding2020/superset-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Superset, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
31 Superset tools catalogued and risk-classified — across an index of 43,000+ MCP servers.