deleteWhiteboard
Delete a whiteboard (the host document and its canvas).
This record as markdown: /tools/io-stablebaseline-sb/deletewhiteboard.md
What deleteWhiteboard does on Stable Baseline
AI agents call deleteWhiteboard 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 |
|---|---|---|---|
documentId | string | Yes |
Parameters from the server's own tool schema.
Why deleteWhiteboard is rated Critical
The tool permanently removes a whiteboard document and its associated canvas content without reversibility. This is irreversible data loss and falls squarely into the Destructive category. While the impact is scoped to a single collaboration artifact rather than critical infrastructure, deletion of shared knowledge/planning documents in a 'company brain' system could disrupt team workflows and lose important context.
From the tool's definition Tool name 'deleteWhiteboard' and description 'Delete a whiteboard (the host document and its canvas)' explicitly perform irreversible deletion of data artifacts.
Attacks that exploit this kind of access
The rule that runs deleteWhiteboard 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 deleteWhiteboard, this is the rule to start with:
deleteWhiteboard 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 deleteWhiteboard call is checked against it from then on.
Questions about deleteWhiteboard
Delete a whiteboard (the host document and its canvas). 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.
deleteWhiteboard accepts 1 parameter: documentId. Required: documentId. 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 deleteWhiteboard: 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.
deleteWhiteboard 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 deleteWhiteboard 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 deleteWhiteboard. 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.
deleteWhiteboard 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