Get detailed information about a specific dashboard including its charts
AI agents call get_dashboard 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 and queries dashboard information including its associated charts. It performs no side effects, does not create, modify, or delete data, and does not execute code or trigger external operations. It is purely informational retrieval, fitting the Read category. Severity is low because dashboard metadata exposure has minimal blast radius in a typical BI environment.
From the tool's definition Tool name 'get_dashboard' and description 'Get detailed information about a specific dashboard including its charts' indicate retrieval of dashboard metadata and configuration without modification.
Attacks that exploit this kind of access
Get detailed information about a specific dashboard including its charts. 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_dashboard: 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_dashboard 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_dashboard 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_dashboard. 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_dashboard 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 →