Searches git commit history using both semantic matching and keyword search. USE WHEN: you need to understand what changed and why — e.g., 'what changed authentication last month?', 'when was the database schema modified?', 'who fixed the login bug?'. Combines two search strategies: (1) semantic ...
Accepts freeform code/query input (query)
Part of the Codegraph MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call codegraph_search_git_history to retrieve information from Codegraph without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though codegraph_search_git_history only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
codegraph_search_git_history:
rules:
- action: allowSee the full Codegraph policy for all 38 tools.
Agents calling read-class tools like codegraph_search_git_history have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Searches git commit history using both semantic matching and keyword search. USE WHEN: you need to understand what changed and why — e.g., 'what changed authentication last month?', 'when was the database schema modified?', 'who fixed the login bug?'. Combines two search strategies: (1) semantic search over git-mined memories (embedding-based, finds conceptually related commits even without keyword overlap), (2) keyword search via git log (catches commits not yet mined into memories). Results include commit hash, subject, author, date, affected files, and memory content when available. Use 'since' to scope results to a time range.. It is categorised as a Read tool in the Codegraph MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for codegraph_search_git_history. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Codegraph MCP server.
codegraph_search_git_history 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 codegraph_search_git_history rule in your Intercept 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 Intercept policy for codegraph_search_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.
codegraph_search_git_history is provided by the Codegraph MCP server (@memoryx/codegraph-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept