Low Risk

github_search

在 GitHub 上搜索仓库、代码、Issues 或用户

Accepts freeform code/query input (query)

Part of the GitHub Search API Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

vaebe/github-search Read Risk 2/5

AI agents call github_search to retrieve information from GitHub Search API Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though github_search only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

vaebe-github-search.yaml
tools:
  github_search:
    rules:
      - action: allow

See the full GitHub Search API Server policy for all 2 tools.

Tool Name github_search
Category Read
Risk Level Low

Agents calling read-class tools like github_search have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the github_search tool do? +

在 GitHub 上搜索仓库、代码、Issues 或用户. It is categorised as a Read tool in the GitHub Search API Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on github_search? +

Add a rule in your Intercept YAML policy under the tools section for github_search. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the GitHub Search API Server MCP server.

What risk level is github_search? +

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

Can I rate-limit github_search? +

Yes. Add a rate_limit block to the github_search rule in your Intercept 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 completely? +

Set action: deny in the Intercept 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.

What MCP server provides github_search? +

github_search is provided by the GitHub Search API Server MCP server (vaebe/github-search). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on GitHub Search API Server

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.