Critical Risk →

delete_calculated_column

Delete one or more calculated columns from a dataset

How to control delete_calculated_column ↓

What delete_calculated_column does on Superset

AI agents call delete_calculated_column 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.

Critical Risk

Why delete_calculated_column needs a policy

The tool performs an irreversible deletion operation on calculated columns within a dataset. This is categorized as Destructive rather than Write because the action cannot be undone and results in permanent loss of column definitions and associated metadata.

From the tool's definition Tool name contains 'delete' and description states 'Delete one or more calculated columns from a dataset' — this is an irreversible removal of data structures.

Documented attack patterns abuse exactly the kind of access delete_calculated_column gives an agent:

How to control delete_calculated_column

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_calculated_column:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_calculated_column"
  ]
}

delete_calculated_column disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Superset — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_calculated_column

What does the delete_calculated_column tool do? +

Delete one or more calculated columns from a dataset. 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.

How do I enforce a policy on delete_calculated_column? +

Register the Superset MCP server in PolicyLayer and add a rule for delete_calculated_column: 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.

What risk level is delete_calculated_column? +

delete_calculated_column is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_calculated_column? +

Yes. Add a rate_limit block to the delete_calculated_column 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.

How do I block delete_calculated_column completely? +

Set action: deny in the PolicyLayer policy for delete_calculated_column. 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.

What MCP server provides delete_calculated_column? +

delete_calculated_column 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.

Enforce policy on every Superset tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.