Busca commits en GitHub por mensaje, autor, fecha, etc.
AI agents call search_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 and queries commit history metadata from GitHub. It performs a passive search operation without creating, modifying, deleting, or executing any code. The blast radius is minimal—worst case, an AI agent retrieves unintended commit information, which poses no security or operational risk.
From the tool's definition Tool name 'search_commits' and description 'Busca commits en GitHub por mensaje, autor, fecha, etc.' (searches commits in GitHub by message, author, date, etc.) indicates a query/retrieval operation with no modification or execution of code.
Attacks that exploit this kind of access
Busca commits en GitHub por mensaje, autor, fecha, etc. 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 search_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.
search_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 search_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 search_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.
search_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 →