Get commit history for a specific file
AI agents call get_file_history to retrieve information from Git Memory MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical metadata about a file's commits without creating, modifying, deleting, or executing any operations. It has no side effects and poses minimal risk even if misused by an AI agent, as the only potential concern is information disclosure of repository history that is typically already accessible to users with repository access.
From the tool's definition Tool name 'get_file_history' and description 'Get commit history for a specific file' indicate a retrieval operation with no modification capability. The verb 'get' and the context of querying historical data confirm this is a read-only query.
Attacks that exploit this kind of access
Get commit history for a specific file. It is categorised as a Read tool in the Git Memory MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Git Memory MCP Server MCP server in PolicyLayer and add a rule for get_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 Memory MCP Server. Nothing to install.
get_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 get_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 get_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.
get_file_history is provided by the Git Memory MCP Server MCP server (nirutyodjai/git-memory-mcp-server). 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 →