collections_unassign_agent
Remove a knowledge collection from an AI agent. The collection and its files are not deleted — only the agent assignment is removed.
This record as markdown: /tools/io-github-saloprj-dialogbrain/collections-unassign-agent.md
What collections_unassign_agent does on Dialogbrain
AI agents use collections_unassign_agent 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 |
|---|---|---|---|
agent_id | integer | Yes | ID of the AI agent |
collection_id | integer | Yes | ID of the collection to unassign |
Parameters from the server's own tool schema.
Why collections_unassign_agent is rated Medium
This tool modifies a relationship (unassigns a collection from an agent) but does not delete any data. The collection and files remain intact. It is a reversible write operation — the assignment can be restored. Severity is medium because removing a knowledge collection from an agent could disrupt agent functionality or responses.
From the tool's definition 'Remove a knowledge collection from an AI agent' and 'only the agent assignment is removed' — modifies the agent-collection relationship without deleting data
Attacks that exploit this kind of access
The rule that runs collections_unassign_agent 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_unassign_agent, this is the rule to start with:
collections_unassign_agent 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_unassign_agent call is checked against it from then on.
Questions about collections_unassign_agent
Remove a knowledge collection from an AI agent. The collection and its files are not deleted — only the agent assignment is removed. 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_unassign_agent accepts 2 parameters: agent_id, collection_id. Required: agent_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_unassign_agent: 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_unassign_agent 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_unassign_agent 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_unassign_agent. 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_unassign_agent 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