list_commits
Get list of commits of a branch in a GitHub repository. Returns at least 30 results per page by default, but can return more if specified using the perPage parameter (up to 100).
This record as markdown: /tools/github/list-commits.md
What list_commits does on GitHub
AI agents call list_commits to retrieve information from GitHub without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
sha | string | — | Commit SHA, branch or tag name to list commits of. If not provided, uses the default branch of the repository. If a commit SHA is provided, will list commits up |
page | number | — | Page number for pagination (min 1) |
repo | string | — | Repository name |
owner | string | — | Repository owner |
author | string | — | Author username or email address to filter commits by |
perPage | number | — | Results per page for pagination (min 1, max 100) |
Parameters from the server's own tool schema.
Why list_commits is rated Low
This tool queries and retrieves commit history from a GitHub repository. It performs no mutations, does not execute code or scripts, and has no destructive effects. The pagination parameters (perPage, after_id visible in sibling tools) are standard read-only query options. The blast radius of misuse is minimal — an agent might retrieve unnecessary commit data but cannot modify, delete, or execute anything.
From the tool's definition Tool name 'list_commits' and description explicitly states it 'Get list of commits' — a retrieval operation with 'Returns...results', indicating query-only behavior with no modification or execution.
Attacks that exploit this kind of access
The rule that runs list_commits safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GitHub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_commits, this is the rule to start with:
list_commits is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every list_commits call is checked against it from then on.
Questions about list_commits
Get list of commits of a branch in a GitHub repository. Returns at least 30 results per page by default, but can return more if specified using the perPage parameter (up to 100). It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.
list_commits accepts 6 parameters: sha, page, repo, owner, author, perPage. The full parameter table on this page comes from the server's own tool schema.
Register the 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 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 GitHub MCP server (oci:ghcr.io/github/github-mcp-server:1.3.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GitHub, and thousands of servers like it.
This server
Across the catalogue