create_calculated_column

THE RISK

Medium Risk

Why create_calculated_column needs a policy

This tool creates new calculated columns in a dataset, which modifies the dataset structure and adds derived data. This is a Write operation because it creates new data artifacts reversibly. Severity is medium because misconfigured calculated columns could affect analytics downstream, but the change is not destructive and does not involve code execution, financial operations, or external system commands.

From the tool's definition Tool name 'create_calculated_column' and description 'Create one or more new calculated columns for a dataset' both indicate data modification. The operation is reversible (columns can be deleted via 'delete_calculated_column').

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

POLICY

How to control create_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 create_calculated_column:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_calculated_column": {
      "limits": [
        {
          "counter": "create_calculated_column_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

create_calculated_column stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

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

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Superset tools

Destructive delete_calculated_column Delete one or more calculated columns from a dataset Destructive delete_dataset Deletes a dataset from Superset. This is a permanent operation and cannot be undone. Be ca Destructive delete_dataset_metric Delete one or more metrics from a dataset Destructive remove_chart_from_dashboard Remove a chart from a dashboard and clean up its layout nodes. Execute execute_sql Execute SQL query using /api/v1/sqllab/execute/ endpoint Execute refresh_dataset_schema Refreshes a dataset Write set_chart_filters Set data filters for a chart. This permanently updates the chart Write find_and_replace_in_sql Performs a simple text find-and-replace on a virtual dataset

All 31 Superset tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about create_calculated_column

What does the create_calculated_column tool do? +

Create one or more new calculated columns for a dataset. It is categorised as a Write tool in the Superset MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_calculated_column? +

Register the Superset MCP server in PolicyLayer and add a rule for create_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 create_calculated_column? +

create_calculated_column is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_calculated_column? +

Yes. Add a rate_limit block to the create_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 create_calculated_column completely? +

Set action: deny in the PolicyLayer policy for create_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 create_calculated_column? +

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

CHECK YOUR STACK →