collections_list
List all knowledge collections in the workspace. Collections are named groups of files used for RAG search. Auto-created collections (per-agent, per-prompt) are hidden by default.
This record as markdown: /tools/io-github-saloprj-dialogbrain/collections-list.md
What collections_list does on Dialogbrain
AI agents call collections_list 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 |
|---|---|---|---|
include_inactive | boolean | — | Include inactive collections. OMIT to list only active collections (the default). |
Parameters from the server's own tool schema.
Why collections_list is rated Low
This tool queries and returns metadata about existing knowledge collections without creating, modifying, deleting, or executing anything. It has no side effects and poses minimal risk even if misused by an AI agent, as it only exposes organizational information about RAG collections.
From the tool's definition Tool name 'collections_list' and description explicitly states it 'List[s] all knowledge collections' — a retrieval operation with no modification or execution. The term 'list' is a canonical Read operation.
Attacks that exploit this kind of access
The rule that runs collections_list 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, this is the rule to start with:
collections_list 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 call is checked against it from then on.
Questions about collections_list
List all knowledge collections in the workspace. Collections are named groups of files used for RAG search. Auto-created collections (per-agent, per-prompt) are hidden by default. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.
collections_list accepts 1 parameter: include_inactive. 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: 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 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 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. 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 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