AI agents call git_log to retrieve information from MCP File Edit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves version control history information. It is a pure read operation that queries git metadata and returns commit logs. There is no ability to modify repositories, execute commands, or cause destructive changes. The blast radius of misuse is minimal—an agent could only gather information about the codebase's history.
From the tool's definition Tool name is 'git_log' and description states 'Get git commit log.' The verb 'Get' indicates data retrieval with no side effects. Git log operations retrieve historical commit information without modifying, executing, or deleting data.
Documented attack patterns abuse exactly the kind of access git_log gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP File Edit, and nothing reaches the server without passing your rules. This is the rule we recommend for git_log:
{
"version": "1",
"default": "deny",
"tools": {
"git_log": {}
}
}git_log 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 git commit log. It is categorised as a Read tool in the MCP File Edit MCP Server, which means it retrieves data without modifying state.
Register the MCP File Edit MCP server in PolicyLayer and add a rule for git_log: 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 MCP File Edit. Nothing to install.
git_log 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 git_log 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 git_log. 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.
git_log is provided by the MCP File Edit MCP server (patrickomatik/mcp-file-edit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP File Edit, 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.
32 MCP File Edit tools catalogued and risk-classified — across an index of 43,000+ MCP servers.