deleteDiagramInDocument
Delete a diagram: removes the database record AND every reference to it in the document body — the current marker format plus legacy forms (markers without an embedded diagramId, and old plain-text [Diagram: name] placeholders). The response's removedFromBody says whether a marker was actually fo...
This record as markdown: /tools/io-stablebaseline-sb/deletediagramindocument.md
What deleteDiagramInDocument does on Stable Baseline
AI agents call deleteDiagramInDocument 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 |
|---|---|---|---|
diagramId | string | Yes | Diagram ID from DIAGRAM_OMITTED markers. |
versionTimestamp | number | — | Optional document optimistic-lock token; validated when provided. (Alias accepted: documentVersionTimestamp.) |
Parameters from the server's own tool schema.
Why deleteDiagramInDocument is rated Critical
This tool irreversibly deletes data (database records) and cannot be undone. It removes both the diagram itself and all references to it within documents. This is a destructive operation that eliminates information permanently.
From the tool's definition Delete a diagram: removes the database record AND every reference to it in the document body — the current marker format plus legacy forms (markers without an embedded diagramId, and old plain-text `[Diagram: name]` placeholders).
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs deleteDiagramInDocument 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 deleteDiagramInDocument, this is the rule to start with:
deleteDiagramInDocument 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 deleteDiagramInDocument call is checked against it from then on.
Questions about deleteDiagramInDocument
Delete a diagram: removes the database record AND every reference to it in the document body — the current marker format plus legacy forms (markers without an embedded diagramId, and old plain-text [Diagram: name] placeholders). The response's removedFromBody says whether a marker was actually found in the body, and versionTimestamp is the document's fresh lock token. 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.
deleteDiagramInDocument accepts 2 parameters: diagramId, versionTimestamp. Required: diagramId. 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 deleteDiagramInDocument: 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.
deleteDiagramInDocument 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 deleteDiagramInDocument 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 deleteDiagramInDocument. 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.
deleteDiagramInDocument 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