🚀 NEW: Git-aware incremental indexing. Only indexes files changed since a git ref (branch/commit). MUCH FASTER than full re-index for large repos. Use this when working on feature branches or after pulling changes. Examples:
AI agents call index_git_changes to retrieve information from MCP Context Manager without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
index_git_changes is a read-only analysis tool that scans git history and file contents to build or update an index for code search. It retrieves and processes data without modifying it. The tool supports the MCP Context Manager's purpose of efficient code navigation through querying, not mutating state.
From the tool's definition Tool indexes (reads) git-changed files and performs analysis-only operations. Description explicitly states 'indexes files changed since a git ref' and references fast querying/scanning of repository metadata.
Documented attack patterns abuse exactly the kind of access index_git_changes gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Context Manager, and nothing reaches the server without passing your rules. This is the rule we recommend for index_git_changes:
{
"version": "1",
"default": "deny",
"tools": {
"index_git_changes": {}
}
}index_git_changes is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
🚀 NEW: Git-aware incremental indexing. Only indexes files changed since a git ref (branch/commit). MUCH FASTER than full re-index for large repos. Use this when working on feature branches or after pulling changes. Examples:. It is categorised as a Read tool in the MCP Context Manager MCP Server, which means it retrieves data without modifying state.
Register the MCP Context Manager MCP server in PolicyLayer and add a rule for index_git_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 MCP Context Manager. Nothing to install.
index_git_changes is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the index_git_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 index_git_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.
index_git_changes is provided by the MCP Context Manager MCP server (transparentlyok/mcp-context-manager). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Context Manager, 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.
21 MCP Context Manager tools catalogued and risk-classified — across an index of 43,000+ MCP servers.