Search for GitHub repositories
AI agents call search_repositories to retrieve information from Server Github without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
page | number | — | Page number for pagination (default: 1) |
query | string | Yes | Search query (see GitHub search syntax) |
perPage | number | — | Number of results per page (default: 30, max: 100) |
Parameters from the server's own tool schema.
The search function is a read-only operation that queries and returns repository metadata. It has no side effects, does not create, modify, or delete data, and does not trigger external operations or financial transactions. The blast radius of misuse is minimal—an attacker could only discover public repository information already available through GitHub's web interface.
From the tool's definition Tool name 'search_repositories' and description 'Search for GitHub repositories' indicate a query operation that retrieves data without modifying state.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
Search for GitHub repositories. It is categorised as a Read tool in the Server Github MCP Server, which means it retrieves data without modifying state.
search_repositories accepts 3 parameters: page, query, perPage. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Server 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 Server 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 Server Github MCP server (@iflow-mcp/server-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 →