High-level summary of any GitHub repo.
AI agents call tool_repo_summary to retrieve information from Codelens-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves information about a public GitHub repository without modifying data, executing code, or triggering external operations. It is purely informational in nature, making it a Read category tool with low severity since misuse would only result in information disclosure of already-public repository data.
From the tool's definition Tool provides 'high-level summary of any GitHub repo' — a retrieval operation with no modification, deletion, or code execution capability. Consistent with sibling tools like tool_repo_info, tool_list_files, and tool_get_file which are all Read operations.
Attacks that exploit this kind of access
High-level summary of any GitHub repo. It is categorised as a Read tool in the Codelens-MCP MCP Server, which means it retrieves data without modifying state.
Register the Codelens- MCP server in PolicyLayer and add a rule for tool_repo_summary: 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 Codelens-MCP. Nothing to install.
tool_repo_summary 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 tool_repo_summary 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 tool_repo_summary. 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.
tool_repo_summary is provided by the Codelens- MCP server (yashkashte5/codelens-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 →