Refresh the dataset schema from the source (rescan columns and types).
AI agents invoke superset_dataset_refresh_schema to trigger actions in MCP Superset. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an external operation against a data source to rescan columns and types. It doesn't merely read or write data reversibly — it initiates a backend process that updates schema metadata by querying the underlying source. This is an Execute-level action. Misuse could cause unintended schema changes or performance impacts, warranting medium severity.
From the tool's definition Refresh the dataset schema from the source (rescan columns and types)
Documented attack patterns abuse exactly the kind of access superset_dataset_refresh_schema gives an agent:
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_dataset_refresh_schema:
{
"version": "1",
"default": "deny",
"tools": {
"superset_dataset_refresh_schema": {
"limits": [
{
"counter": "superset_dataset_refresh_schema_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}superset_dataset_refresh_schema stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Refresh the dataset schema from the source (rescan columns and types). It is categorised as a Execute tool in the MCP Superset MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Superset MCP server in PolicyLayer and add a rule for superset_dataset_refresh_schema: 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.
superset_dataset_refresh_schema is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the superset_dataset_refresh_schema 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.
Set action: deny in the PolicyLayer policy for superset_dataset_refresh_schema. 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.
superset_dataset_refresh_schema 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.
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.