collections_list_files
List all files in a knowledge collection with their indexing status and chunk counts. Each returned file has a file_id (integer) that can be passed to messages.send as attachments=[file_id] to send the file to a contact, or to files.read to read its text content.
This record as markdown: /tools/io-github-saloprj-dialogbrain/collections-list-files.md
What collections_list_files does on Dialogbrain
AI agents call collections_list_files to retrieve information from Dialogbrain without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
collection_id | integer | Yes | ID of the collection |
Parameters from the server's own tool schema.
Why collections_list_files is rated Low
This tool retrieves and queries file metadata from a knowledge collection without side effects. It is a straightforward listing operation that returns file information for reference purposes. The file_id it returns can be used by other tools (send, read) but this tool itself only reads/lists data. This aligns with the 'Read' category definition of retrieving or querying data with no side effects.
From the tool's definition Tool description states it 'List all files' and returns metadata about files including 'file_id', 'indexing status', and 'chunk counts'. The capability is purely informational/retrievalal with no modification, deletion, or execution capability.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs collections_list_files 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_list_files, this is the rule to start with:
collections_list_files is read-only, so it stays allowed. 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_list_files call is checked against it from then on.
Questions about collections_list_files
List all files in a knowledge collection with their indexing status and chunk counts. Each returned file has a file_id (integer) that can be passed to messages.send as attachments=[file_id] to send the file to a contact, or to files.read to read its text content. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.
collections_list_files accepts 1 parameter: collection_id. Required: 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_list_files: 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_list_files is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the collections_list_files 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_list_files. 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_list_files 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