Returns the N most recent commits that touched a file, each annotated with its associated pull request and linked issues.
AI agents call file_history to retrieve information from Git Context without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only query tool that retrieves historical commit data and associated metadata. It has no side effects on the repository, cannot execute code, and does not modify or delete any data. The blast radius of misuse is minimal — an agent might retrieve unwanted historical information but cannot alter the codebase or trigger any external actions.
From the tool's definition Tool returns git commit history and metadata (pull requests, linked issues) for a file with no modification, deletion, or execution capability. The description explicitly states 'Returns' — a retrieval operation.
Attacks that exploit this kind of access
Returns the N most recent commits that touched a file, each annotated with its associated pull request and linked issues. It is categorised as a Read tool in the Git Context MCP Server, which means it retrieves data without modifying state.
Register the Git Context MCP server in PolicyLayer and add a rule for file_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 Git Context. Nothing to install.
file_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 file_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.
Set action: deny in the PolicyLayer policy for file_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.
file_history is provided by the Git Context MCP server (muhannad-hash/git-context-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 →