Get a list of commits of a branch in a repository
AI agents call list_commits to retrieve information from GitHub See MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns commit history information from a repository. It is a read-only operation that retrieves existing data without creating, modifying, deleting, or executing any changes. The blast radius of misuse is minimal—an agent could only enumerate commit information, which is typically public or already accessible to authorized users.
From the tool's definition Tool name 'list_commits' and description 'Get a list of commits of a branch in a repository' indicate a retrieval operation with no data modification or side effects.
Attacks that exploit this kind of access
Get a list of commits of a branch in a repository. It is categorised as a Read tool in the GitHub See MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub See MCP Server 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 See MCP Server. 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 See MCP Server MCP server (jesusmaster/github-see-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 →