Low Risk

github_search

github_search

How to control github_search ↓

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

Low Risk

GitHub search tools query publicly available repository data, issues, pull requests, or code without modifying anything. This is a read operation with no side effects. Severity is low because search results are informational.

From the tool's definition Tool name 'github_search' indicates a search operation against GitHub repositories or content. The naming convention (search verb) and context within a gateway providing 'search, analysis' capabilities strongly suggest read-only data retrieval.

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

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

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

github_search 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 Proxima — 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.

Go deeper

What does the github_search tool do? +

github_search. It is categorised as a Read tool in the Proxima MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on github_search? +

Register the Proxima 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 Proxima. Nothing to install.

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 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 completely? +

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.

What MCP server provides github_search? +

github_search is provided by the Proxima MCP server (zen4-bit/proxima). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Proxima tool call.

Deterministic rules across all 50 Proxima tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

50 Proxima tools catalogued and risk-classified — across an index of 42,500+ 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.