git_blame

Show line-by-line authorship information for a file

SERVERGitHub MCP Server SOURCE0xshariq/github-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0xshariq-github-mcp-server/git-blame.md

WHAT IT DOES

What git_blame does on GitHub MCP Server

AI agents call git_blame to retrieve information from GitHub MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why git_blame is rated Low

git_blame is a read-only operation that queries version control history to attribute code lines to their authors. It has no side effects, does not modify repository state, and does not execute or delete data. This is a standard Read classification for information retrieval tools.

From the tool's definition 'Show line-by-line authorship information for a file' — the tool retrieves and displays git blame data without modifying, deleting, or executing any code. It is purely informational.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs git_blame safely

PolicyLayer is an MCP gateway: it sits between your AI agents and GitHub MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For git_blame, this is the rule to start with:

git_blame Allowed

git_blame 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_blame": {}
  }
}

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

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

FAQ

Questions about git_blame

What does the git_blame tool do? +

Show line-by-line authorship information for a file. It is categorised as a Read tool in the GitHub MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on git_blame? +

Register the GitHub MCP Server MCP server in PolicyLayer and add a rule for git_blame: 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 GitHub MCP Server. Nothing to install.

What risk level is git_blame? +

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

Can I rate-limit git_blame? +

Yes. Add a rate_limit block to the git_blame 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_blame completely? +

Set action: deny in the PolicyLayer policy for git_blame. 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_blame? +

git_blame is provided by the GitHub MCP Server MCP server (0xshariq/github-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on GitHub MCP Server, and thousands of servers like it.

This server

All 33 GitHub MCP Server 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 →