Summarize git commits and hotspots from the last N days. Default is 5 days.
AI agents call get_recent_git_changes to retrieve information from Project Context Map without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query of git history to provide summaries of recent commits and code activity hotspots. It retrieves information without modifying, executing, or deleting any data. The default 5-day window is a parameter for filtering historical data. No side effects or irreversible actions are possible.
From the tool's definition Tool description states 'Summarize git commits and hotspots' — a query operation that retrieves and summarizes historical git data with no side effects. The verb 'summarize' indicates data retrieval, and the context confirms it reads repository history.
Attacks that exploit this kind of access
Summarize git commits and hotspots from the last N days. Default is 5 days. It is categorised as a Read tool in the Project Context Map MCP Server, which means it retrieves data without modifying state.
Register the Project Context Map MCP server in PolicyLayer and add a rule for get_recent_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 Project Context Map. Nothing to install.
get_recent_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 get_recent_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 get_recent_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.
get_recent_git_changes is provided by the Project Context Map MCP server (tamojit-123/project-context-map-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →