github_search_code
AI agents call github_search_code to retrieve information from Integrations MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Code search is a non-destructive query operation that retrieves existing data from GitHub without creating, modifying, or deleting anything. No side effects occur from invoking this tool. While the description is empty, the tool name itself is sufficiently clear and unambiguous. Confidence is slightly reduced due to lack of description, but the semantic meaning of 'search' is well-established as a Read operation.
From the tool's definition Tool name 'github_search_code' clearly indicates a search operation. The verb 'search' is a classic Read category operation that queries data without modification. GitHub's search_code API retrieves matching code snippets from repositories.
Attacks that exploit this kind of access
github_search_code. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.
Register the Integrations MCP server in PolicyLayer and add a rule for github_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 Integrations MCP. Nothing to install.
github_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 github_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 github_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.
github_search_code is provided by the Integrations MCP server (shriram-vasudevan/integrations-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 →