search_code
A read tool on the GitHub MCP server.
This record as markdown: /tools/io-github-aifity-omnigit-mcp/search-code.md
What search_code does on GitHub
AI agents call search_code to retrieve information from GitHub without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why search_code is rated Low
This tool queries or retrieves code from repositories without modifying, executing, or deleting anything. It is a straightforward read operation that returns search results. The low severity reflects that an AI agent misusing this tool could at worst retrieve sensitive code, which is a confidentiality concern but lacks the blast radius of write, execute, or destructive operations.
From the tool's definition Tool name is 'search_code' with description 'Search code'. The verb 'search' indicates a read-only retrieval operation with no data modification, creation, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs search_code safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GitHub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_code, this is the rule to start with:
search_code 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 GitHub, apply this rule, and every search_code call is checked against it from then on.
Questions about search_code
search_code is a read tool on the GitHub MCP server. It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.
Register the GitHub MCP server in PolicyLayer and add a rule for search_code: 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 GitHub. Nothing to install.
search_code 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_code 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_code. 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_code is provided by the GitHub MCP server (oci:ghcr.io/aifity/omnigit-mcp:0.5.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GitHub, and thousands of servers like it.
This server
Across the catalogue