Get list of commits of a branch in a GitHub repository
AI agents call list_commits to retrieve information from Zerops Documentation MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical commit information from a GitHub repository, which is a passive query with no side effects. It does not create, modify, delete, or execute any operations—it only fetches and displays existing data. The blast radius of misuse is minimal, as reading commit history poses no direct risk to system integrity or data stability.
From the tool's definition Tool name 'list_commits' and description 'Get list of commits of a branch in a GitHub repository' indicate a read-only retrieval operation with no modification or deletion of data.
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 Zerops Documentation MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Zerops Documentation 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 Zerops Documentation 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 Zerops Documentation MCP Server MCP server (nermalcat69/zerops-mcp). 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 →