Low Risk

get_dataset_metrics

Get all metrics for a specified dataset

How to control get_dataset_metrics ↓

What get_dataset_metrics does on Superset

AI agents call get_dataset_metrics to retrieve information from Superset without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_dataset_metrics needs a policy

This tool retrieves metrics associated with a dataset. It is a read-only operation that queries and returns information without creating, modifying, deleting, or executing anything. No data is altered, and there are no destructive or financial implications. Low severity because the blast radius of misuse is minimal — an agent can only retrieve existing metrics data.

From the tool's definition Tool name is 'get_dataset_metrics' and description states 'Get all metrics for a specified dataset' — uses retrieval verb 'Get', performs a query operation with no modifications or side effects.

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

How to control get_dataset_metrics

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_dataset_metrics": {}
  }
}

get_dataset_metrics is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  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.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_dataset_metrics

What does the get_dataset_metrics tool do? +

Get all metrics for a specified dataset. 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_dataset_metrics? +

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

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

Can I rate-limit get_dataset_metrics? +

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

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

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