Get repository statistics including contributor stats, commit activity, code frequency, and participation data.
AI agents call get_repo_stats 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 performs data retrieval only. It queries and returns repository metadata and statistics without creating, modifying, deleting, or executing any operations. The language ('Get', 'stats', 'data') confirms read-only semantics.
From the tool's definition Tool name 'get_repo_stats' and description states it retrieves 'repository statistics including contributor stats, commit activity, code frequency, and participation data' — these are read-only query operations with no mention of modifications or side effects.
Attacks that exploit this kind of access
Get repository statistics including contributor stats, commit activity, code frequency, and participation data. 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_stats: 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_stats 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_stats 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_stats. 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_stats 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 →