Show commit history. Displays a log of commits in reverse chronological order, optionally limited to a specific file
AI agents call git_log to retrieve information from Git MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
git_log queries and retrieves historical commit data without creating, modifying, or deleting any repository content. It is a read-only operation with no side effects, fitting the Read category. Severity is low because exposure of commit history poses minimal immediate risk; an AI could at worst review information already in the repository.
From the tool's definition Tool description states 'Show commit history' and 'Displays a log of commits' — purely informational retrieval with no modifications to repository state.
Attacks that exploit this kind of access
Show commit history. Displays a log of commits in reverse chronological order, optionally limited to a specific file. It is categorised as a Read tool in the Git MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Git MCP Server 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 Git MCP Server. 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 Git MCP Server MCP server (wty0512/git-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 →