git_shortlog

Show commit count by author.

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/git-shortlog.md

WHAT IT DOES

What git_shortlog does on Yaver

AI agents call git_shortlog 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
`directory`	string	—

Parameters from the server's own tool schema.

RISK

Why git_shortlog is rated Low

This tool only reads and displays commit statistics from git history. It performs a query operation (similar to 'git shortlog') that has no side effects, produces no state changes, and cannot damage or alter data. The read-only nature and limited blast radius if misused (only exposes commit metadata) justify low severity.

From the tool's definition Tool description states 'Show commit count by author' - a retrieval operation that queries git history and aggregates data without modifying, executing, or deleting anything.

Risk signalsAccepts file system path (directory)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs git_shortlog 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_shortlog, this is the rule to start with:

git_shortlog Allowed

git_shortlog is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "git_shortlog": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every git_shortlog call is checked against it from then on.

FAQ

Questions about git_shortlog

What does the git_shortlog tool do? +

Show commit count by author. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does git_shortlog accept? +

git_shortlog accepts 1 parameter: directory. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on git_shortlog? +

Register the Yaver MCP server in PolicyLayer and add a rule for git_shortlog: 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.

What risk level is git_shortlog? +

git_shortlog is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit git_shortlog? +

Yes. Add a rate_limit block to the git_shortlog 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.

How do I block git_shortlog completely? +

Set action: deny in the PolicyLayer policy for git_shortlog. 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.

What MCP server provides git_shortlog? +

git_shortlog 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.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools →

Across the catalogue

claude_git_status on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →