AI agents use ingest_documents to create or update resources in Qdrant — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Qdrant environment.
The tool name combined with the server's stated purpose of ingesting local documents and generating embeddings strongly suggests this tool creates/writes new vector data into Qdrant. The description is empty, so confidence is reduced, but the sibling tools (delete_documents_by_path, list_category, list_path, search_documents) confirm a CRUD pattern where ingest_documents is the write/create operation.
From the tool's definition Tool name 'ingest_documents' and server description mentioning 'document ingestion' and 'generating embeddings with OpenAI'
Attacks that exploit this kind of access
ingest_documents. It is categorised as a Write tool in the Qdrant MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Qdrant MCP server in PolicyLayer and add a rule for ingest_documents: 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 Qdrant. Nothing to install.
ingest_documents 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 ingest_documents 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 ingest_documents. 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.
ingest_documents is provided by the Qdrant MCP server (msstnk/qdrant-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →