Index a codebase for semantic code search. Automatically discovers files, chunks code intelligently using AST-aware parsing, and stores in vector database. Respects .gitignore and other ignore files.
AI agents use index_codebase 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 reads files from a codebase and writes/stores chunked representations into the vector database. It creates new data (embeddings and indexed chunks) in the database, which is a Write operation. Severity is high because it can ingest an entire codebase into the vector database, potentially storing sensitive source code, and could overwrite or pollute existing indexed data at scale.
From the tool's definition Index a codebase...Automatically discovers files, chunks code intelligently using AST-aware parsing, and stores in vector database
Documented attack patterns abuse exactly the kind of access index_codebase 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_codebase:
{
"version": "1",
"default": "deny",
"tools": {
"index_codebase": {
"limits": [
{
"counter": "index_codebase_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}index_codebase 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.
Index a codebase for semantic code search. Automatically discovers files, chunks code intelligently using AST-aware parsing, and stores in vector database. Respects .gitignore and other ignore files. 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_codebase: 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_codebase 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_codebase 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_codebase. 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_codebase 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.