git_stats
Show your git contribution stats — commits, lines, top files, languages.
This record as markdown: /tools/io-github-kivanccakmak-yaver/git-stats.md
What git_stats does on Yaver
AI agents call git_stats to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
days | integer | — | Days to analyze (default: 30) |
directory | string | — |
Parameters from the server's own tool schema.
Why git_stats is rated Low
This tool queries and presents existing git metadata (commits, lines changed, file information, language statistics). It is a read-only operation that retrieves information from a git repository with no side effects, data modification, code execution, or destructive capability. The blast radius of misuse is minimal—an agent could only gain visibility into developer activity patterns.
From the tool's definition Tool name 'git_stats' and description 'Show your git contribution stats — commits, lines, top files, languages' indicate it retrieves and displays git repository statistics without modification or execution of code.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs git_stats safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For git_stats, this is the rule to start with:
git_stats is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every git_stats call is checked against it from then on.
Questions about git_stats
Show your git contribution stats — commits, lines, top files, languages. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
git_stats accepts 2 parameters: days, directory. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for git_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 Yaver. Nothing to install.
git_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_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_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_stats is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue