Get list of commits of a branch in a GitHub repository
AI agents call list_commits to retrieve information from Server Github without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
sha | string | — | |
page | number | — | |
repo | string | Yes | |
owner | string | Yes | |
perPage | number | — |
Parameters from the server's own tool schema.
This is a read-only operation that queries and returns commit history. It has no side effects, does not create, modify, or delete any data. The blast radius of misuse is minimal—an agent could only retrieve commit information that is typically already publicly visible or accessible to authenticated users with appropriate permissions.
From the tool's definition Tool name is 'list_commits' and description states it 'Get list of commits of a branch in a GitHub repository'. This retrieves historical commit data without modifying any repository state.
Attacks that exploit this kind of access
Get list of commits of a branch in a GitHub repository. It is categorised as a Read tool in the Server Github MCP Server, which means it retrieves data without modifying state.
list_commits accepts 5 parameters: sha, page, repo, owner, perPage. Required: repo, owner. The full parameter table on this page comes from the server's own tool schema.
Register the Server Github MCP server in PolicyLayer and add a rule for list_commits: 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 Server Github. Nothing to install.
list_commits 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 list_commits 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 list_commits. 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.
list_commits is provided by the Server Github MCP server (@iflow-mcp/server-github). 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 →