delete_dashboard

Delete a dashboard (table) within a database. Removes the table and its data. Use get_database_detail first to see available dashboards.

Server Fusebase MCP Server ryan-haver/fusebase-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What delete_dashboard does on Fusebase MCP Server

AI agents call delete_dashboard to permanently remove resources in Fusebase MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_dashboard needs a policy

The tool irreversibly deletes a dashboard/table and its associated data. This is a destructive operation that cannot be undone, matching the Destructive category definition. The high severity reflects that data loss is a significant blast radius if triggered incorrectly by an AI agent. The confidence is high because the description explicitly states deletion and data removal.

From the tool's definition Delete a dashboard (table) within a database. Removes the table and its data.

Questions about delete_dashboard

What does the delete_dashboard tool do? +

Delete a dashboard (table) within a database. Removes the table and its data. Use get_database_detail first to see available dashboards. It is categorised as a Destructive tool in the Fusebase MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_dashboard? +

Register the Fusebase MCP Server MCP server in PolicyLayer and add a rule for delete_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 Fusebase MCP Server. Nothing to install.

What risk level is delete_dashboard? +

delete_dashboard is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_dashboard? +

Yes. Add a rate_limit block to the delete_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.

How do I block delete_dashboard completely? +

Set action: deny in the PolicyLayer policy for delete_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.

What MCP server provides delete_dashboard? +

delete_dashboard is provided by the Fusebase MCP Server MCP server (ryan-haver/fusebase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.