Critical Risk →

superset_user_delete

superset_user_delete

How to control superset_user_delete ↓

What superset_user_delete does on MCP Superset

AI agents call superset_user_delete to permanently remove resources in MCP Superset — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why superset_user_delete needs a policy

The tool performs an irreversible deletion operation on user entities in a Superset system. User deletion cannot be undone and permanently removes user accounts and associated permissions/configurations. This qualifies as Destructive rather than Write.

From the tool's definition Tool name 'superset_user_delete' explicitly indicates deletion of user accounts. The 'delete' operation is irreversible and removes data that cannot be undone.

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

How to control superset_user_delete

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Superset, and nothing reaches the server without passing your rules. This is the rule we recommend for superset_user_delete:

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

superset_user_delete 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 MCP 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 superset_user_delete

What does the superset_user_delete tool do? +

superset_user_delete. It is categorised as a Destructive tool in the MCP 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 superset_user_delete? +

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

What risk level is superset_user_delete? +

superset_user_delete 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 superset_user_delete? +

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

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

superset_user_delete is provided by the MCP Superset MCP server (mcp-superset). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Superset tool call.

Start from MCP 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.

137 MCP 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.