folders_delete
🗑️ Delete an inbox folder. Threads inside become unfiled (not deleted). When to use: - User wants to remove a folder they no longer need - User wants to clean up their inbox organization Threads inside the folder are NOT deleted — they simply move back to the inbox.
This record as markdown: /tools/io-github-saloprj-dialogbrain/folders-delete.md
What folders_delete does on Dialogbrain
AI agents call folders_delete to permanently remove resources in Dialogbrain, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
folder_id | integer | Yes | ID of the folder to delete |
Parameters from the server's own tool schema.
Why folders_delete is rated Critical
The tool performs an irreversible deletion of a folder object. While threads are not deleted, the folder deletion cannot be undone and represents data destruction. This qualifies as Destructive rather than Write because it permanently removes an organizational structure without reversibility.
From the tool's definition Tool name contains 'delete' and description states '🗑️ Delete an inbox folder.' This is an irreversible deletion operation that destroys the folder structure itself, even though contained threads are preserved.
Attacks that exploit this kind of access
The rule that runs folders_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For folders_delete, this is the rule to start with:
folders_delete 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 Dialogbrain, apply this rule, and every folders_delete call is checked against it from then on.
Questions about folders_delete
🗑️ Delete an inbox folder. Threads inside become unfiled (not deleted). When to use: - User wants to remove a folder they no longer need - User wants to clean up their inbox organization Threads inside the folder are NOT deleted — they simply move back to the inbox. It is categorised as a Destructive tool in the Dialogbrain MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
folders_delete accepts 1 parameter: folder_id. Required: folder_id. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain MCP server in PolicyLayer and add a rule for folders_delete: 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 Dialogbrain. Nothing to install.
folders_delete 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 folders_delete 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 folders_delete. 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.
folders_delete is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dialogbrain, and thousands of servers like it.
Across the catalogue