index_git_history

THE RISK

Medium Risk

Why index_git_history needs a policy

Indexing a repository involves reading git history and writing document embeddings into the vector database. This is a Write operation as it creates new entries in the database. It is reversible (can be cleared with clear_git_index). Severity is medium due to the potential to ingest large amounts of data or sensitive repository content into the vector store.

From the tool's definition 'Index a repository' — this tool reads git history and writes/creates index entries in the Qdrant vector database

Documented attack patterns abuse exactly the kind of access index_git_history gives an agent:

POLICY

How to control index_git_history

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_git_history:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "index_git_history": {
      "limits": [
        {
          "counter": "index_git_history_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

index_git_history 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.

Create a free account and register Qdrant MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Qdrant MCP Server tools

Destructive clear_git_index Delete all indexed git history data for a repository. This is irreversible and will remove Destructive clear_index Delete all indexed data for a codebase. This is irreversible and will remove the entire co Destructive delete_collection Delete a collection and all its documents. Destructive delete_documents Delete specific documents from a collection by their IDs. Write index_new_commits Incrementally index only new commits since the last indexing. Much faster than full re-ind Write index_codebase Index a codebase for semantic code search. Automatically discovers files, chunks code inte Write reindex_changes Incrementally re-index only changed files. Detects added, modified, and deleted files sinc Write add_documents Add documents to a collection. Documents will be automatically embedded using the configur

All 20 Qdrant MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about index_git_history

What does the index_git_history tool do? +

Index a repository. 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.

How do I enforce a policy on index_git_history? +

Register the Qdrant MCP Server MCP server in PolicyLayer and add a rule for index_git_history: 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.

What risk level is index_git_history? +

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

Can I rate-limit index_git_history? +

Yes. Add a rate_limit block to the index_git_history 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 index_git_history completely? +

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

index_git_history 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.

Enforce policy on every Qdrant MCP Server tool call.

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.

CHECK YOUR STACK →