deleteDocument
Delete a document.
This record as markdown: /tools/io-stablebaseline-sb/deletedocument.md
What deleteDocument does on Stable Baseline
AI agents call deleteDocument 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 |
|---|---|---|---|
projectId | string | — | Optional. Narrows a friendly-id lookup to one project. Ignored when documentId is a UUID. |
documentId | string | Yes |
Parameters from the server's own tool schema.
Why deleteDocument is rated Critical
Deleting a document is a destructive action that cannot be undone. It permanently removes data from the system. This matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' The severity is high because deletion of documents in a company knowledge management system could result in loss of critical business information, plans, or records.
From the tool's definition Tool name 'deleteDocument' and description 'Delete a document.' explicitly indicate irreversible deletion of data.
Attacks that exploit this kind of access
The rule that runs deleteDocument 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 deleteDocument, this is the rule to start with:
deleteDocument 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 deleteDocument call is checked against it from then on.
Questions about deleteDocument
Delete a document. 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.
deleteDocument accepts 2 parameters: projectId, 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 deleteDocument: 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.
deleteDocument 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 deleteDocument 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 deleteDocument. 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.
deleteDocument 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