collections_create
Create a named knowledge collection. Collections group files for RAG search. After creating, add files with collections.add_file and assign to agents with collections.assign_agent.
This record as markdown: /tools/io-github-saloprj-dialogbrain/collections-create.md
What collections_create does on Dialogbrain
AI agents use collections_create 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 |
|---|---|---|---|
name | string | Yes | Collection name (must be unique per user) |
description | string | — | Optional description of the collection |
Parameters from the server's own tool schema.
Why collections_create is rated Medium
This tool creates metadata (a named collection) but does not execute code, retrieve sensitive data, delete anything, or move money. It is a reversible write operation that organizes knowledge for later use. Severity is low because creating a collection has minimal blast radius—it simply establishes an organizational structure with no direct impact on existing data or external systems.
From the tool's definition Tool description explicitly states 'Create a named knowledge collection' — a create operation that establishes new data structures for RAG (retrieval-augmented generation) workflows.
Attacks that exploit this kind of access
The rule that runs collections_create 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_create, this is the rule to start with:
collections_create 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_create call is checked against it from then on.
Questions about collections_create
Create a named knowledge collection. Collections group files for RAG search. After creating, add files with collections.add_file and assign to agents with collections.assign_agent. 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_create accepts 2 parameters: name, description. Required: name. 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_create: 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_create 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_create 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_create. 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_create 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