Get statistics about the Git repository cache, including number of cached repositories and total size.
AI agents call git_cache_stats to retrieve information from CodeRAG without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns cache statistics (count of cached repositories and total size). It is purely informational with no capability to modify, delete, or execute operations. It falls clearly into the Read category as it retrieves data about the cache state without side effects.
From the tool's definition Tool name 'git_cache_stats' and description 'Get statistics about the Git repository cache' indicate a retrieval operation. The verb 'Get' and the nature of statistics—which are informational queries—confirm no data modification or side effects.
Documented attack patterns abuse exactly the kind of access git_cache_stats gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CodeRAG, and nothing reaches the server without passing your rules. This is the rule we recommend for git_cache_stats:
{
"version": "1",
"default": "deny",
"tools": {
"git_cache_stats": {}
}
}git_cache_stats is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get statistics about the Git repository cache, including number of cached repositories and total size. It is categorised as a Read tool in the CodeRAG MCP Server, which means it retrieves data without modifying state.
Register the CodeRAG MCP server in PolicyLayer and add a rule for git_cache_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 CodeRAG. Nothing to install.
git_cache_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 git_cache_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 git_cache_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.
git_cache_stats is provided by the CodeRAG MCP server (jonnoc/coderag). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CodeRAG, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
38 CodeRAG tools catalogued and risk-classified — across an index of 43,000+ MCP servers.