Get dashboard details and embedded configuration in a single response.
AI agents call get_dashboard_config 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.
This tool retrieves dashboard configuration and details without creating, modifying, deleting, or executing anything. It is a simple query operation with no side effects, fitting the 'Read' category for data retrieval. Low severity because accessing dashboard configuration poses minimal risk even if exposed to an AI agent—it is informational only.
From the tool's definition Tool name 'get_dashboard_config' and description 'Get dashboard details and embedded configuration' indicate data retrieval with no modification or execution. The verb 'get' and lack of any action words suggest a read-only operation.
Documented attack patterns abuse exactly the kind of access get_dashboard_config 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 get_dashboard_config:
{
"version": "1",
"default": "deny",
"tools": {
"get_dashboard_config": {}
}
}get_dashboard_config is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get dashboard details and embedded configuration in a single response. It is categorised as a Read tool in the Superset MCP Server, which means it retrieves data without modifying state.
Register the Superset MCP server in PolicyLayer and add a rule for get_dashboard_config: 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.
get_dashboard_config 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_config 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_config. 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_config 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.