Low Risk

search_repositories

Search for GitHub repositories

How to control search_repositories ↓

What search_repositories does on GitHub MCP Server Plus

AI agents call search_repositories to retrieve information from GitHub MCP Server Plus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why search_repositories needs a policy

This tool performs a search query to find and list repositories, which is a read-only operation with no side effects. It matches the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).' The blast radius is minimal as it only returns publicly discoverable information.

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 anything.

Documented attack patterns abuse exactly the kind of access search_repositories gives an agent:

How to control search_repositories

PolicyLayer is an MCP gateway — it sits between your AI agents and GitHub MCP Server Plus, and nothing reaches the server without passing your rules. This is the rule we recommend for search_repositories:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_repositories": {}
  }
}

search_repositories is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register GitHub MCP Server Plus — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about search_repositories

What does the search_repositories tool do? +

Search for GitHub repositories. It is categorised as a Read tool in the GitHub MCP Server Plus MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_repositories? +

Register the GitHub MCP Server Plus 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 GitHub MCP Server Plus. Nothing to install.

What risk level is search_repositories? +

search_repositories is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_repositories? +

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.

How do I block search_repositories completely? +

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.

What MCP server provides search_repositories? +

search_repositories is provided by the GitHub MCP Server Plus MCP server (phialsbasement/mcp-github-server-plus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every GitHub MCP Server Plus tool call.

Start from GitHub MCP Server Plus, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

18 GitHub MCP Server Plus tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.