get_commit_history

Get commit history for a repository. Supports filtering by branch, file path, author, and date range. Returns paginated results with commit details.

Server Mcp Github sheeryn123/mcp-github-server
Category Read
Risk class Low
Parameters 00 required

What get_commit_history does on Mcp Github

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

Why get_commit_history needs a policy

This tool retrieves historical commit information from a repository with filtering capabilities. It performs read-only queries without modifying code, triggering deployments, or deleting data. The filtering parameters (branch, file path, author, date range) are all read-only query inputs. No side effects or irreversible actions are possible.

From the tool's definition Tool name 'get_commit_history' and description 'Get commit history for a repository...Returns paginated results with commit details' indicate data retrieval with no modification or side effects.

Questions about get_commit_history

What does the get_commit_history tool do? +

Get commit history for a repository. Supports filtering by branch, file path, author, and date range. Returns paginated results with commit details. It is categorised as a Read tool in the Mcp Github MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_commit_history? +

Register the Mcp Github MCP server in PolicyLayer and add a rule for get_commit_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 Mcp Github. Nothing to install.

What risk level is get_commit_history? +

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

Can I rate-limit get_commit_history? +

Yes. Add a rate_limit block to the get_commit_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.

How do I block get_commit_history completely? +

Set action: deny in the PolicyLayer policy for get_commit_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.

What MCP server provides get_commit_history? +

get_commit_history is provided by the Mcp Github MCP server (sheeryn123/mcp-github-server). 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.