Incrementally re-index only changed files. Detects added, modified, and deleted files since last index. Requires previous indexing with index_codebase.
AI agents use reindex_changes to create or update resources in Qdrant MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Qdrant MCP Server environment.
This tool updates the vector database index by processing changed files — adding new embeddings, updating modified ones, and removing deleted ones. While it does delete stale index entries, its primary purpose is keeping the index current (a write/update operation). The deletions are of index entries (derived data), not source documents, making Write the most appropriate category.
From the tool's definition Incrementally re-index only changed files. Detects added, modified, and deleted files since last index.
Documented attack patterns abuse exactly the kind of access reindex_changes gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Qdrant MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for reindex_changes:
{
"version": "1",
"default": "deny",
"tools": {
"reindex_changes": {
"limits": [
{
"counter": "reindex_changes_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}reindex_changes 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.
Free to start. No card required.
Incrementally re-index only changed files. Detects added, modified, and deleted files since last index. Requires previous indexing with index_codebase. It is categorised as a Write tool in the Qdrant MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Qdrant MCP Server MCP server in PolicyLayer and add a rule for reindex_changes: 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 MCP Server. Nothing to install.
reindex_changes 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 reindex_changes 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 reindex_changes. 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.
reindex_changes is provided by the Qdrant MCP Server MCP server (mhalder/qdrant-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Qdrant MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 Qdrant MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.