git_log

Show git commit history

Server Coding MCP Server kieutrongthien/coding-mcp
Category Read
Risk class Low
Parameters 00 required

What git_log does on Coding MCP Server

AI agents call git_log to retrieve information from Coding MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why git_log needs a policy

git_log is a read-only operation that queries and displays Git commit history. It does not modify, delete, or execute any code; it merely retrieves and presents existing data. Even in a production environment, viewing commit history poses minimal risk to system integrity or data safety.

From the tool's definition Tool name is 'git_log' and description states 'Show git commit history' — this retrieves historical commit information with no modifications, deletions, or side effects.

Questions about git_log

What does the git_log tool do? +

Show git commit history. It is categorised as a Read tool in the Coding MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on git_log? +

Register the Coding 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 Coding MCP Server. Nothing to install.

What risk level is git_log? +

git_log is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit git_log? +

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.

How do I block git_log completely? +

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.

What MCP server provides git_log? +

git_log is provided by the Coding MCP Server MCP server (kieutrongthien/coding-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.