Show git commit history with detailed information
AI agents call git_log to retrieve information from MCP Workspace Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
git_log retrieves and displays historical git commit information. This is a read-only operation that queries existing data without side effects, modification, or code execution. The tool does not create, delete, modify data, or execute arbitrary commands. Severity is low because the blast radius of misuse is limited to information disclosure of commit history, which is typically non-sensitive in most contexts.
From the tool's definition Tool name 'git_log' and description 'Show git commit history with detailed information' indicate retrieval of version control metadata with no modification or execution.
Attacks that exploit this kind of access
Show git commit history with detailed information. It is categorised as a Read tool in the MCP Workspace Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Workspace 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 MCP Workspace 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 MCP Workspace Server MCP server (shayyeffet/ultimate_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 →