deleteFolder
Delete a folder recursively, including all nested folders and documents.
This record as markdown: /tools/io-stablebaseline-sb/deletefolder.md
What deleteFolder does on Stable Baseline
AI agents call deleteFolder 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 |
|---|---|---|---|
folderId | string | Yes |
Parameters from the server's own tool schema.
Why deleteFolder is rated Critical
deleteFolder performs irreversible data destruction. The recursive nature and comprehensive scope (folders AND all nested documents) make this a destructive action that could permanently erase significant portions of the company knowledge base. While not financial in nature, the potential loss of critical documentation, plans, and organizational knowledge represents high severity.
From the tool's definition Tool description states "Delete a folder recursively, including all nested folders and documents" — this is an irreversible deletion operation that cannot be undone and has broad blast radius (affects folder hierarchy and all contained data).
Attacks that exploit this kind of access
The rule that runs deleteFolder 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 deleteFolder, this is the rule to start with:
deleteFolder 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 deleteFolder call is checked against it from then on.
Questions about deleteFolder
Delete a folder recursively, including all nested folders and documents. 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.
deleteFolder accepts 1 parameter: folderId. Required: folderId. 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 deleteFolder: 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.
deleteFolder 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 deleteFolder 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 deleteFolder. 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.
deleteFolder 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