Lista commits de un repositorio o branch específico
AI agents call list_commits 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.
This tool retrieves commit history from a repository or branch without creating, modifying, deleting, or executing any code. It has no side effects and presents minimal security risk as it only queries existing data. Severity is low because commit history is typically non-sensitive metadata in public or authorized repositories.
From the tool's definition Tool name is 'list_commits' and description states 'Lista commits de un repositorio o branch específico' (List commits from a specific repository or branch). The verb 'list' and the lack of any modification language indicate a retrieval operation.
Attacks that exploit this kind of access
Lista commits de un repositorio o branch específico. It is categorised as a Read tool in the Mcp Github MCP Server, which means it retrieves data without modifying state.
Register the Mcp 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 Mcp 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 Mcp Github MCP server (pblarismendi/mcp-github-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 →