github_search_repositories

Search for repositories

SERVERSage MCP SOURCEsagemcp/sagemcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sagemcp-sagemcp/github-search-repositories.md

WHAT IT DOES

What github_search_repositories does on Sage MCP

AI agents call github_search_repositories to retrieve information from Sage MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why github_search_repositories is rated Low

This tool queries GitHub's repository search functionality to retrieve matching repositories. It does not create, modify, delete, or execute any operations. The search function is a read-only retrieval operation that returns data without changing state or triggering external actions.

From the tool's definition Tool name is 'github_search_repositories' and description states 'Search for repositories' — a retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs github_search_repositories safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For github_search_repositories, this is the rule to start with:

github_search_repositories Allowed

github_search_repositories is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "github_search_repositories": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sage MCP, apply this rule, and every github_search_repositories call is checked against it from then on.

FAQ

Questions about github_search_repositories

What does the github_search_repositories tool do? +

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

How do I enforce a policy on github_search_repositories? +

Register the Sage MCP server in PolicyLayer and add a rule for github_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 Sage MCP. Nothing to install.

What risk level is github_search_repositories? +

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

Can I rate-limit github_search_repositories? +

Yes. Add a rate_limit block to the github_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 github_search_repositories completely? +

Set action: deny in the PolicyLayer policy for github_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 github_search_repositories? +

github_search_repositories is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sage, and thousands of servers like it.

This server

All 359 Sage tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →search_circuits on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →