Calculates aggregate statistics across all repositories including:
AI agents call get_repository_stats to retrieve information from GitInsight-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and aggregates statistics from repositories without creating, modifying, deleting, or executing any operations. It is a read-only data retrieval function that poses minimal security risk if misused by an AI agent, as it only exposes historical, public-facing repository metadata and analytics.
From the tool's definition Tool name is 'get_repository_stats' and description indicates it 'Calculates aggregate statistics across all repositories' — purely retrieval and analysis of existing data with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Calculates aggregate statistics across all repositories including:. It is categorised as a Read tool in the GitInsight-MCP MCP Server, which means it retrieves data without modifying state.
Register the GitInsight- MCP server in PolicyLayer and add a rule for get_repository_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 GitInsight-MCP. Nothing to install.
get_repository_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_repository_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_repository_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_repository_stats is provided by the GitInsight- MCP server (marwaniiwael18/gitinsight-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 →