Search for GitHub repositories
AI agents call search_repositories 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 queries GitHub's repository search API to find and list repositories matching specified criteria. It has no side effects—it does not create, modify, delete, or execute anything. The blast radius of misuse is minimal; an attacker could enumerate repositories but cannot access private data without authorization or take destructive actions. Classification as Read is appropriate.
From the tool's definition Tool name 'search_repositories' and description 'Search for GitHub repositories' indicate a query operation that retrieves repository metadata without modifying or executing code. The use of 'search' and 'for' aligns with read-only data retrieval.
Attacks that exploit this kind of access
Search for GitHub repositories. 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_repositories: 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_repositories 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_repositories 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_repositories. 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_repositories is provided by the Mcp Github MCP server (@missionsquad/mcp-github). 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 →