search_github
Search GitHub repositories by query, topic, language, and star count. Useful for discovering libraries, frameworks, prior art, and learning from existing implementations. Returns repo metadata including stars, forks, description, and topics. GITHUB_TOKEN optional but recommended for higher rate l...
This record as markdown: /tools/io-github-homenshum-nodebench/search-github.md
What search_github does on Nodebench
AI agents call search_github to retrieve information from Nodebench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why search_github is rated Low
This tool only queries public GitHub data and returns metadata—it does not create, modify, delete, or execute any code. It is a straightforward information retrieval operation with no side effects. The optional GITHUB_TOKEN parameter is purely for rate-limit management, not authorization of write/execute actions. Severity is low because misuse would only result in accessing public repository information.
From the tool's definition Tool performs a search query on GitHub repositories and 'Returns repo metadata including stars, forks, description, and topics.' No mutations or side effects mentioned. The verb 'Search' and 'discovering' indicate read-only retrieval.
Attacks that exploit this kind of access
The rule that runs search_github safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_github, this is the rule to start with:
search_github 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 Nodebench, apply this rule, and every search_github call is checked against it from then on.
Questions about search_github
Search GitHub repositories by query, topic, language, and star count. Useful for discovering libraries, frameworks, prior art, and learning from existing implementations. Returns repo metadata including stars, forks, description, and topics. GITHUB_TOKEN optional but recommended for higher rate limits. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.
Register the Nodebench MCP server in PolicyLayer and add a rule for search_github: 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 Nodebench. Nothing to install.
search_github 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_github 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_github. 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_github is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue