files_ingest
Save and index a file into the knowledge base. Use this when the user asks to save, store, or remember a document. The file will be processed (OCR if needed) and indexed for future search.
This record as markdown: /tools/io-github-saloprj-dialogbrain/files-ingest.md
What files_ingest does on Dialogbrain
AI agents use files_ingest 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 |
|---|---|---|---|
tags | array | — | Optional list of tags for categorization (e.g., ['presentation', 'dextrade']). |
title | string | — | Human-readable title for the file (e.g., 'Project Presentation', 'Q1 Report'). If not provided, uses original filename. |
file_id | integer | Yes | ID of the file to ingest (from attachment_file_ids in context). |
thread_id | integer | — | Optional thread ID to associate the file with. If not provided, uses context thread. |
description | string | — | Optional description of the file contents. |
Parameters from the server's own tool schema.
Why files_ingest is rated Medium
This tool creates new indexed file records in a knowledge base, which is a reversible write operation. It does not execute arbitrary code, delete data irreversibly, or move money.
From the tool's definition 'Save and index a file into the knowledge base' — the tool creates and modifies data (indexed file records) in a persistent knowledge base.
Attacks that exploit this kind of access
The rule that runs files_ingest 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 files_ingest, this is the rule to start with:
files_ingest 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 files_ingest call is checked against it from then on.
Questions about files_ingest
Save and index a file into the knowledge base. Use this when the user asks to save, store, or remember a document. The file will be processed (OCR if needed) and indexed for future search. 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.
files_ingest accepts 5 parameters: tags, title, file_id, thread_id, description. Required: file_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 files_ingest: 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.
files_ingest 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 files_ingest 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 files_ingest. 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.
files_ingest 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