Get the commit history for a specific file. Returns commits that touched the file, sorted by date (newest first). Faster than git log for indexed repositories.
AI agents call file_history to retrieve information from Local Rag without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure read operation that queries git commit metadata and presents it to the user. It has no side effects, does not execute code, and does not modify or delete data. The blast radius if misused by an AI agent is minimal—at worst, it reads information that is already publicly available in the repository's version history.
From the tool's definition Tool 'file_history' retrieves commit history for a file, returning commits 'sorted by date (newest first)' with no modification or deletion of any data. The description explicitly states it 'returns' historical information.
Documented attack patterns abuse exactly the kind of access file_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Local Rag, and nothing reaches the server without passing your rules. This is the rule we recommend for file_history:
{
"version": "1",
"default": "deny",
"tools": {
"file_history": {}
}
}file_history 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.
Get the commit history for a specific file. Returns commits that touched the file, sorted by date (newest first). Faster than git log for indexed repositories. It is categorised as a Read tool in the Local Rag MCP Server, which means it retrieves data without modifying state.
Register the Local Rag 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 Local Rag. 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 Local Rag MCP server (thewinci/mimirs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Local Rag, 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.
29 Local Rag tools catalogued and risk-classified — across an index of 43,000+ MCP servers.