Fetch data from an existing chart
AI agents call get_chart_data to retrieve information from Superset MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries data from an already-created chart in Superset. It performs no mutations, deletions, code execution, or financial operations. The action is purely informational and reversible by nature (reading does not change state). Blast radius is minimal—an agent fetching chart data poses negligible risk compared to tools like execute_sql, create_chart, or delete operations on the same server.
From the tool's definition Tool name is 'get_chart_data' and description states 'Fetch data from an existing chart' — both indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Fetch data from an existing chart. It is categorised as a Read tool in the Superset MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Superset MCP Server MCP server in PolicyLayer and add a rule for get_chart_data: 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 MCP Server. Nothing to install.
get_chart_data is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_chart_data 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 get_chart_data. 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.
get_chart_data is provided by the Superset MCP Server MCP server (okybaguslukmana/superset-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →