This record as markdown: /tools/io-github-kivanccakmak-yaver/git-blame-file.md
What git_blame_file does on Yaver
AI agents call git_blame_file 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 |
|---|---|---|---|
file | string | Yes | |
lines | string | — | Line range (e.g. 10,20) |
Parameters from the server's own tool schema.
Why git_blame_file is rated Low
git blame is a read-only git command that queries and displays authorship and change history information for a file. It does not create, modify, delete, or execute anything—it only retrieves and presents existing version control metadata. This falls squarely under the Read category with low severity since it has no side effects and the blast radius of misuse is minimal.
From the tool's definition Tool name 'git_blame_file' and description 'Show line-by-line blame' indicate retrieval of git history metadata without modification.
Risk signalsAccepts file system path (file)
Attacks that exploit this kind of access
The rule that runs git_blame_file 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_blame_file, this is the rule to start with:
git_blame_file 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_blame_file call is checked against it from then on.
Questions about git_blame_file
Show line-by-line blame. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
git_blame_file accepts 2 parameters: file, lines. Required: file. 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_blame_file: 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_blame_file 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_blame_file 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_blame_file. 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_blame_file 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