Update chart properties including metadata, datasource, and visualization settings. This tool replaces the old update_chart_params with a unified interface that accepts object format params and can modify any chart property. IMPORTANT: When updating visualization parameters, first call
AI agents use update_chart to create or update resources in Superset — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Superset environment.
This tool modifies existing chart configurations without deleting them, making it a Write operation. Severity is high because an AI agent could maliciously alter visualization settings, datasource connections, or metadata across multiple charts used in dashboards and reports, potentially corrupting analytical outputs or redirecting data sources.
From the tool's definition Tool description explicitly states it 'Update[s] chart properties' and 'can modify any chart property', including 'metadata, datasource, and visualization settings'. The verb 'update' and 'modify' indicate reversible state changes.
Documented attack patterns abuse exactly the kind of access update_chart gives an agent:
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 update_chart:
{
"version": "1",
"default": "deny",
"tools": {
"update_chart": {
"limits": [
{
"counter": "update_chart_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_chart stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update chart properties including metadata, datasource, and visualization settings. This tool replaces the old update_chart_params with a unified interface that accepts object format params and can modify any chart property. IMPORTANT: When updating visualization parameters, first call. It is categorised as a Write tool in the Superset MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Superset MCP server in PolicyLayer and add a rule for update_chart: 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.
update_chart is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_chart 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 update_chart. 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.
update_chart 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.
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.