superset_dashboard_filter_delete

THE RISK

Critical Risk

Why superset_dashboard_filter_delete needs a policy

This tool performs an irreversible deletion operation on dashboard filter objects. Once deleted, the filter configuration cannot be recovered without manual restoration. This fits the Destructive category (delete, drop, purge, force-push).

From the tool's definition Tool name contains 'delete' and description states 'Delete a native filter from a dashboard by ID.' The action irreversibly removes a filter configuration from a dashboard.

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

POLICY

How to control superset_dashboard_filter_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_dashboard_filter_delete:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "superset_dashboard_filter_delete"
  ]
}

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

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

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP Superset tools

Destructive superset_annotation_delete Delete an annotation from a layer. Destructive superset_annotation_layer_delete Delete an annotation layer along with all its annotations. Destructive superset_bulk_user_role_remove superset_bulk_user_role_remove Destructive superset_chart_delete Delete a chart by ID. The chart will be removed from all dashboards. Destructive superset_dashboard_delete Delete a dashboard by ID. Charts and datasets are NOT deleted — only the dashboard itself. Destructive superset_dashboard_embedded_delete Disable dashboard embedding (embedded mode). Destructive superset_dashboard_revoke_role_access superset_dashboard_revoke_role_access Destructive superset_database_delete superset_database_delete

All 137 MCP Superset tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in MCP Superset → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about superset_dashboard_filter_delete

What does the superset_dashboard_filter_delete tool do? +

Delete a native filter from a dashboard by ID. 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_dashboard_filter_delete? +

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

superset_dashboard_filter_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_dashboard_filter_delete? +

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

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

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

CHECK YOUR STACK →