get_file_blame
Get git blame for a file at a given ref. Each entry maps a contiguous range of source lines to the commit that last changed them (id, author, authored_date, message). Use range_start/range_end to limit blame to specific lines.
This record as markdown: /tools/io-github-zereight-gitlab-mcp/get-file-blame.md
What get_file_blame does on Gitlab Mcp
AI agents call get_file_blame to retrieve information from Gitlab Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_file_blame is rated Low
This is a read-only query operation that retrieves historical metadata about code changes. It has no side effects and does not create, modify, delete, or execute anything. The optional range_start/range_end parameters only filter the scope of the read, not the nature of the operation. Severity is low because exposure of blame history poses minimal risk—it is typically public information in version control systems.
From the tool's definition Tool retrieves git blame information (commit id, author, authored_date, message) for a file without modifying data. Description uses 'Get' and the operation is purely informational—it maps source lines to commits that changed them.
Attacks that exploit this kind of access
The rule that runs get_file_blame safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gitlab Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_file_blame, this is the rule to start with:
get_file_blame 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 Gitlab Mcp, apply this rule, and every get_file_blame call is checked against it from then on.
Questions about get_file_blame
Get git blame for a file at a given ref. Each entry maps a contiguous range of source lines to the commit that last changed them (id, author, authored_date, message). Use range_start/range_end to limit blame to specific lines. It is categorised as a Read tool in the Gitlab Mcp MCP Server, which means it retrieves data without modifying state.
Register the Gitlab MCP server in PolicyLayer and add a rule for get_file_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 Gitlab Mcp. Nothing to install.
get_file_blame 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 get_file_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.
Set action: deny in the PolicyLayer policy for get_file_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.
get_file_blame is provided by the Gitlab MCP server (@zereight/mcp-gitlab). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gitlab, and thousands of servers like it.
This server
Across the catalogue