collections_add_file
Add a file to a knowledge collection. The file must be uploaded and indexed first (files_upload + files_ingest). If the file was previously removed, it is re-enabled.
This record as markdown: /tools/io-github-saloprj-dialogbrain/collections-add-file.md
What collections_add_file does on Dialogbrain
AI agents use collections_add_file to create or update resources in Dialogbrain, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dialogbrain environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
file_id | integer | Yes | ID of the file to add (from files_upload) |
collection_id | integer | Yes | ID of the collection |
Parameters from the server's own tool schema.
Why collections_add_file is rated Medium
This tool modifies data (a knowledge collection) by adding or re-enabling file associations. It is reversible (files can be removed), so it falls under Write rather than Destructive. Severity is medium because unauthorized addition of files to collections could pollute knowledge bases or expose sensitive information to AI agents, but the impact is localized to the collection and reversible.
From the tool's definition Tool 'collections_add_file' creates or modifies a knowledge collection by adding a file to it. Description states it 'Add[s] a file to a knowledge collection' and can 're-enable' previously removed files, indicating reversible state changes.
Attacks that exploit this kind of access
The rule that runs collections_add_file 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 collections_add_file, this is the rule to start with:
collections_add_file stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Dialogbrain, apply this rule, and every collections_add_file call is checked against it from then on.
Questions about collections_add_file
Add a file to a knowledge collection. The file must be uploaded and indexed first (files_upload + files_ingest). If the file was previously removed, it is re-enabled. It is categorised as a Write tool in the Dialogbrain MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
collections_add_file accepts 2 parameters: file_id, collection_id. Required: file_id, collection_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 collections_add_file: 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.
collections_add_file is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the collections_add_file 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 collections_add_file. 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.
collections_add_file 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.
This server
Across the catalogue