get_dashboard_filters

THE RISK

Low Risk

Why get_dashboard_filters needs a policy

This tool retrieves dashboard filter information without modifying, executing, or deleting any data. It is a pure read operation with no side effects or blast radius if misused by an AI agent. The low severity reflects that dashboard filter metadata is typically not sensitive operational data.

From the tool's definition Tool name 'get_dashboard_filters' and description 'Get the dashboard' indicate retrieval of dashboard filter configuration data with no modification capability.

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

POLICY

How to control get_dashboard_filters

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_dashboard_filters": {}
  }
}

get_dashboard_filters is read-only, so it stays allowed — but 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.

CAP 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 →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_dashboard_filters

What does the get_dashboard_filters tool do? +

Get the dashboard. It is categorised as a Read tool in the Superset MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_dashboard_filters? +

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

get_dashboard_filters is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_dashboard_filters? +

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

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

get_dashboard_filters 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 →