Возвращает статистику проиндексированного репозитория.
AI agents call repo_stats to retrieve information from Booster MCP 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, querying existing repository statistics with no side effects, no code execution, and no modifications to the codebase or system. It is purely informational and aligns with the 'Read' category definition of retrieving or querying data without side effects (analogous to 'get' or 'fetch' operations).
From the tool's definition Tool description states it 'returns statistics of an indexed repository' (repo_stats returns статистику — statistics). It retrieves and queries pre-computed repository data without modifying or executing anything.
Attacks that exploit this kind of access
Возвращает статистику проиндексированного репозитория. It is categorised as a Read tool in the Booster MCP MCP Server, which means it retrieves data without modifying state.
Register the Booster MCP server in PolicyLayer and add a rule for 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 Booster MCP. Nothing to install.
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 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 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.
repo_stats is provided by the Booster MCP server (neuroghostdev/booster_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 →