Search for code across GitHub repositories
AI agents call search-code to retrieve information from GitHub Enterprise MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries code content from repositories without creating, modifying, deleting, or executing anything. It is a read-only search operation with minimal blast radius if misused by an AI agent—worst case being excessive API calls or exposure of sensitive code patterns already visible in the repository.
From the tool's definition Tool name 'search-code' combined with description 'Search for code across GitHub repositories' indicates a query operation with no modification or execution of code.
Attacks that exploit this kind of access
Search for code across GitHub repositories. It is categorised as a Read tool in the GitHub Enterprise MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub Enterprise MCP Server 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 Enterprise MCP Server. 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 Enterprise MCP Server MCP server (lessinthought/github-enterprice-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →