git_info
Get git repository information. Operations: status (changed files), diff (diff stats), log (last 20 commits), branch (all branches), remote (remote URLs).
This record as markdown: /tools/io-github-kivanccakmak-yaver/git-info.md
What git_info does on Yaver
AI agents call git_info 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 | — | Git repo directory (default: agent work dir) |
operation | string | Yes | Git operation: status, diff, log, branch, remote |
Parameters from the server's own tool schema.
Why git_info is rated Low
git_info purely retrieves and queries git repository information without side effects. No data is created, modified, deleted, or executed. The tool is informational only, making it a Read category risk with low severity since exposing git history and branch information has minimal blast radius in a local dev environment.
From the tool's definition Tool description states operations are: 'status (changed files), diff (diff stats), log (last 20 commits), branch (all branches), remote (remote URLs)' - all read-only queries of git repository metadata with no modification, deletion, or execution capability.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs git_info 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_info, this is the rule to start with:
git_info 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_info call is checked against it from then on.
Questions about git_info
Get git repository information. Operations: status (changed files), diff (diff stats), log (last 20 commits), branch (all branches), remote (remote URLs). It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
git_info accepts 2 parameters: directory, operation. Required: operation. 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_info: 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_info 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_info 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_info. 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_info 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