Incrementally index only new commits since the last indexing. Much faster than full re-indexing when keeping the index up to date with recent changes.
AI agents use index_new_commits 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 writes new data (commit indexes) to the vector database. It creates/updates index entries for new commits but does not delete existing data, making it a Write operation. Misuse could result in incorrect or unwanted data being indexed into the vector database, but effects are reversible (indexed data can be deleted).
From the tool's definition Incrementally index only new commits since the last indexing
Documented attack patterns abuse exactly the kind of access index_new_commits 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 index_new_commits:
{
"version": "1",
"default": "deny",
"tools": {
"index_new_commits": {
"limits": [
{
"counter": "index_new_commits_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}index_new_commits 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 index only new commits since the last indexing. Much faster than full re-indexing when keeping the index up to date with recent changes. 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 index_new_commits: 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.
index_new_commits 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 index_new_commits 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 index_new_commits. 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.
index_new_commits 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.