search_repos
Search GitHub repositories (GitHub search syntax).
This record as markdown: /tools/io-github-abhishekkumar2021-github/search-repos.md
What search_repos does on GitHub
AI agents call search_repos to retrieve information from GitHub without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | |
query | string | Yes |
Parameters from the server's own tool schema.
Why search_repos is rated Low
This tool retrieves repository metadata using GitHub's search syntax. It performs a read-only query operation with no capability to modify, create, delete, or execute code. The blast radius of misuse is minimal — an agent could only access information about public/authorized repositories, which does not constitute a security breach on its own.
From the tool's definition Tool name is 'search_repos' and description states 'Search GitHub repositories' — a query operation with no side effects. Searching is a retrieval action that does not modify, execute, or delete data.
Attacks that exploit this kind of access
The rule that runs search_repos safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GitHub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_repos, this is the rule to start with:
search_repos is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every search_repos call is checked against it from then on.
Questions about search_repos
Search GitHub repositories (GitHub search syntax). It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.
search_repos accepts 2 parameters: limit, query. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the GitHub MCP server in PolicyLayer and add a rule for search_repos: 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 GitHub. Nothing to install.
search_repos 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_repos 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_repos. 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_repos is provided by the GitHub MCP server (@abhishekmcp/github). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GitHub, and thousands of servers like it.
This server
Across the catalogue