This record as markdown: /tools/io-github-2s-io-mcp/code.repo-lookup.md
What code.repo-lookup does on Mcp
AI agents call code.repo-lookup to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why code.repo-lookup is rated Low
This tool retrieves information about public GitHub repositories. It is a read-only query operation with no side effects, data modification, code execution, or financial implications. The lookup of public repository data poses minimal security risk to the system or data integrity.
From the tool's definition Tool name 'repo-lookup' and description 'Look up a public GitHub repository' indicates retrieval of publicly available repository metadata without modification.
Attacks that exploit this kind of access
The rule that runs code.repo-lookup safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For code.repo-lookup, this is the rule to start with:
code.repo-lookup 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 Mcp, apply this rule, and every code.repo-lookup call is checked against it from then on.
Questions about code.repo-lookup
Look up a public GitHub repository by. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for code.repo-lookup: 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 Mcp. Nothing to install.
code.repo-lookup 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 code.repo-lookup 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 code.repo-lookup. 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.
code.repo-lookup is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue