Create a new dashboard in Superset
AI agents use create_dashboard to create or update resources in Superset MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Superset MCP Server environment.
Creating a dashboard is a reversible write operation—it adds a new resource to the system that can later be modified or deleted. It does not execute code, delete data irreversibly, or commit financial transactions. The blast radius is moderate because a compromised AI agent could create many dashboards and consume system resources, but the operation itself is non-destructive and can be undone.
From the tool's definition Tool name and description indicate creation of a new dashboard resource: 'Create a new dashboard in Superset'. This is a write operation that creates a new persistent entity in the system.
Attacks that exploit this kind of access
Create a new dashboard in Superset. It is categorised as a Write tool in the Superset MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Superset MCP Server MCP server in PolicyLayer and add a rule for create_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.
create_dashboard 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 create_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 create_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.
create_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 →