files_delete
Permanently delete files from this workspace by their IDs (generated documents, uploads, screenshots, etc.). IRREVERSIBLE: removes the DB record, detaches every reference (knowledge collections, thread pins, message attachments), and deletes the stored blob. There is no undo. Use to clean up left...
This record as markdown: /tools/io-github-saloprj-dialogbrain/files-delete.md
What files_delete does on Dialogbrain
AI agents call files_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 |
|---|---|---|---|
file_ids | array | Yes | List of file IDs to permanently delete (max 20). |
Parameters from the server's own tool schema.
Why files_delete is rated Critical
An AI agent that decides to call files_delete doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Dialogbrain is gone. There is no undo for destructive operations.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs files_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 files_delete, this is the rule to start with:
files_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 files_delete call is checked against it from then on.
Questions about files_delete
Permanently delete files from this workspace by their IDs (generated documents, uploads, screenshots, etc.). IRREVERSIBLE: removes the DB record, detaches every reference (knowledge collections, thread pins, message attachments), and deletes the stored blob. There is no undo. Use to clean up leftover / superseded generated files. Only files that belong to this workspace are touched; unknown or other-workspace ids are returned under not_found. Max 20 per call. 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.
files_delete accepts 1 parameter: file_ids. Required: file_ids. 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 files_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.
files_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 files_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 files_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.
files_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