github_search
[SUPPORT] Search GitHub — a REAL external lookup (keyless), sibling to paper_search/social_search for external prior-art / competitive-repo research. Distinct from search_code, which only searches the CALLING project's own connected repo. Two keyless endpoints via the 'type' param: 'code' (defaul...
This record as markdown: /tools/io-github-ajc3xc-meridian/github-search.md
What github_search does on Meridian
AI agents call github_search to retrieve information from Meridian 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 |
|---|---|---|---|
type | string | — | Which keyless GitHub endpoint to search (default 'code'). |
limit | integer | — | Max results to return (default 10, max 50). |
query | string | Yes | Search terms (GitHub search-qualifier syntax is accepted, e.g. 'language:python foo'). |
sort_by | string | — | Sort order (default relevance; 'date' = most recently indexed/updated first). |
Parameters from the server's own tool schema.
Why github_search is rated Low
github_search is a read-only query tool that retrieves and returns public GitHub data without side effects. It searches external repositories and code patterns but does not execute code, create/modify data, delete data, or engage in financial transactions.
From the tool's definition Tool description explicitly states it performs 'external lookup (keyless)' via 'GitHub Code Search' and 'GitHub Repository Search', returning query results with metadata (title, authors, summary, url, etc.).
Attacks that exploit this kind of access
The rule that runs github_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meridian, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For github_search, this is the rule to start with:
github_search 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 Meridian, apply this rule, and every github_search call is checked against it from then on.
Questions about github_search
[SUPPORT] Search GitHub — a REAL external lookup (keyless), sibling to paper_search/social_search for external prior-art / competitive-repo research. Distinct from search_code, which only searches the CALLING project's own connected repo. Two keyless endpoints via the 'type' param: 'code' (default; GitHub Code Search — actual usage of a symbol/pattern/API across public repos) and 'repo' (GitHub Repository Search — competitor/prior-art repositories by topic/description/stars). Returns {query, count, results:[{title, authors, summary, published, url, ...}]} — code rows carry path/repo/sha/score, repo rows carry repo/stars/forks/language/score. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.
github_search accepts 4 parameters: type, limit, query, sort_by. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Meridian MCP server in PolicyLayer and add a rule for github_search: 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 Meridian. Nothing to install.
github_search 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 github_search 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 github_search. 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.
github_search is provided by the Meridian MCP server (@meridianmcp/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meridian, and thousands of servers like it.
This server
Across the catalogue