vcs_blame
Per-line last-change attribution for a file: for each line, the short commit, author, ISO date, and the line text. Optionally restrict to a [start,end] line range (1-based, inclusive). Read-only.
This record as markdown: /tools/breakpoint-mcp/vcs-blame.md
What vcs_blame does on Breakpoint
AI agents call vcs_blame to retrieve information from Breakpoint 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 |
|---|---|---|---|
end | integer | — | Last line (1-based, inclusive) |
path | string | Yes | File to blame (res:// or repo-relative) |
start | integer | — | First line (1-based, inclusive) |
Parameters from the server's own tool schema.
Why vcs_blame is rated Low
The tool retrieves version control blame/attribution data for a file. It is explicitly described as read-only and only returns metadata (commit, author, date, line text) without modifying anything.
From the tool's definition Per-line last-change attribution for a file... Read-only.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs vcs_blame safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vcs_blame, this is the rule to start with:
vcs_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 Breakpoint, apply this rule, and every vcs_blame call is checked against it from then on.
Questions about vcs_blame
Per-line last-change attribution for a file: for each line, the short commit, author, ISO date, and the line text. Optionally restrict to a [start,end] line range (1-based, inclusive). Read-only. It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.
vcs_blame accepts 3 parameters: end, path, start. Required: path. The full parameter table on this page comes from the server's own tool schema.
Register the Breakpoint MCP server in PolicyLayer and add a rule for vcs_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 Breakpoint. Nothing to install.
vcs_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 vcs_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 vcs_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.
vcs_blame is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
This server
Across the catalogue