deleteDatabase
Move a whole database, one of its tables (pass table) or one of its dashboards (pass dashboard) to the trash. It can be restored in the app for 30 days, after which it is gone for good. A database or a table goes with every row in it and needs admin access; a dashboard needs write access. A table...
This record as markdown: /tools/io-stablebaseline-sb/deletedatabase.md
What deleteDatabase does on Stable Baseline
AI agents call deleteDatabase to permanently remove resources in Stable Baseline, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
table | string | — | Delete only this table (its id or name). |
dashboard | string | — | Move only this dashboard (its id or name) to the trash. |
databaseId | string | Yes | The database's id, friendly id (DB-12) or exact name. |
Parameters from the server's own tool schema.
Why deleteDatabase is rated Critical
An AI agent that decides to call deleteDatabase doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Stable Baseline is gone. There is no undo for destructive operations.
Risk signalsBulk/mass operation — affects multiple targets · Admin/system-level operation
Attacks that exploit this kind of access
The rule that runs deleteDatabase safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stable Baseline, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For deleteDatabase, this is the rule to start with:
deleteDatabase is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Stable Baseline, apply this rule, and every deleteDatabase call is checked against it from then on.
Questions about deleteDatabase
Move a whole database, one of its tables (pass table) or one of its dashboards (pass dashboard) to the trash. It can be restored in the app for 30 days, after which it is gone for good. A database or a table goes with every row in it and needs admin access; a dashboard needs write access. A table that another table links to cannot be deleted until that link is removed. To take a page or a visual out of a dashboard, use saveDatabaseDashboard. getDatabaseGuide topic deleting. It is categorised as a Destructive tool in the Stable Baseline MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
deleteDatabase accepts 3 parameters: table, dashboard, databaseId. Required: databaseId. The full parameter table on this page comes from the server's own tool schema.
Register the Stable Baseline MCP server in PolicyLayer and add a rule for deleteDatabase: 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 Stable Baseline. Nothing to install.
deleteDatabase is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the deleteDatabase 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 deleteDatabase. 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.
deleteDatabase is provided by the Stable Baseline MCP server (https://api.stablebaseline.io/functions/v1/cloud-serve/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stable Baseline, and thousands of servers like it.
Across the catalogue