ingest_file

Ingest a document file (PDF, DOCX, TXT, MD) into the vector database. Path must be absolute; re-ingesting the same path replaces its existing data. Returns { filePath, chunkCount, timestamp, fileTitle }.

Server Mcp Local Rag mcp-local-rag
Category Write
Risk class Medium
Parameters 00 required

What ingest_file does on Mcp Local Rag

AI agents use ingest_file to create or update resources in Mcp Local Rag — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Local Rag environment.

Why ingest_file needs a policy

This tool writes new data into a vector database by chunking and indexing a document. The replacement behavior on re-ingestion is a form of overwrite, but it is reversible in the sense that the original file remains on disk and the operation can be re-done. It does not delete records irreversibly without replacement, so Write is the appropriate category.

From the tool's definition 'Ingest a document file into the vector database' and 're-ingesting the same path replaces its existing data'

Questions about ingest_file

What does the ingest_file tool do? +

Ingest a document file (PDF, DOCX, TXT, MD) into the vector database. Path must be absolute; re-ingesting the same path replaces its existing data. Returns { filePath, chunkCount, timestamp, fileTitle }. It is categorised as a Write tool in the Mcp Local Rag MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on ingest_file? +

Register the Mcp Local Rag MCP server in PolicyLayer and add a rule for ingest_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 Mcp Local Rag. Nothing to install.

What risk level is ingest_file? +

ingest_file is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit ingest_file? +

Yes. Add a rate_limit block to the ingest_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.

How do I block ingest_file completely? +

Set action: deny in the PolicyLayer policy for ingest_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.

What MCP server provides ingest_file? +

ingest_file is provided by the Mcp Local Rag MCP server (mcp-local-rag). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

ingest_file is one line of Mcp Local Rag's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.