Get detailed information about a GitHub repository including stats, topics, license, and recent activity.
AI agents call get_repo_info to retrieve information from Mcp Github without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns metadata about a repository (stats, topics, license, recent activity). It performs no write operations, does not execute code or commands, does not delete data, and involves no financial transactions. It is a straightforward data retrieval operation with no side effects, fitting the Read category with low severity.
From the tool's definition Tool description states it 'Get[s] detailed information about a GitHub repository including stats, topics, license, and recent activity' — purely retrieves data with no modification or execution of code.
Attacks that exploit this kind of access
Get detailed information about a GitHub repository including stats, topics, license, and recent activity. It is categorised as a Read tool in the Mcp Github MCP Server, which means it retrieves data without modifying state.
Register the Mcp Github MCP server in PolicyLayer and add a rule for get_repo_info: 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 Github. Nothing to install.
get_repo_info 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 get_repo_info 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 get_repo_info. 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.
get_repo_info is provided by the Mcp Github MCP server (sheeryn123/mcp-github-server). 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 →