agents_remove_file
Remove a file from this agent's private knowledge. The file itself is not deleted — it's just detached from this agent. Use agents.list_files to find the file_id to remove.
This record as markdown: /tools/io-github-saloprj-dialogbrain/agents-remove-file.md
What agents_remove_file does on Dialogbrain
AI agents use agents_remove_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 detach (from agents.list_files) |
agent_id | integer | Yes | ID of the agent to remove the file from |
Parameters from the server's own tool schema.
Why agents_remove_file is rated Medium
The tool modifies an agent's configuration by detaching a file from its knowledge base, but explicitly states the file itself is not deleted. This is a reversible modification (the file can be re-attached), placing it in the Write category rather than Destructive. Misuse could degrade agent performance by removing knowledge files, hence medium severity.
From the tool's definition Remove a file from this agent's private knowledge. The file itself is not deleted — it's just detached from this agent.
Attacks that exploit this kind of access
The rule that runs agents_remove_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 agents_remove_file, this is the rule to start with:
agents_remove_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 agents_remove_file call is checked against it from then on.
Questions about agents_remove_file
Remove a file from this agent's private knowledge. The file itself is not deleted — it's just detached from this agent. Use agents.list_files to find the file_id to remove. 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.
agents_remove_file accepts 2 parameters: file_id, agent_id. Required: file_id, agent_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 agents_remove_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.
agents_remove_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 agents_remove_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 agents_remove_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.
agents_remove_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