vcs_diff

Unified diff of the working tree (default) or the staged index (staged=true), optionally scoped to a single path (res:// or project-relative). Returns the patch (tail-truncated) plus the changed-file list, both project-relative. A path matching nothing is refused, not answered empty. Read-only.

SERVERBreakpoint SOURCEbreakpoint-mcp

Low RISK CLASS

Category Read

Parameters 20 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/breakpoint-mcp/vcs-diff.md

WHAT IT DOES

What vcs_diff does on Breakpoint

AI agents call vcs_diff 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
`path`	string	—	Restrict the diff to this path (res:// or project-relative)
`staged`	boolean	—	Diff the staged index vs HEAD instead of the working tree (default false)

Parameters from the server's own tool schema.

RISK

Why vcs_diff is rated Low

Even though vcs_diff only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsAccepts file system path (path)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs vcs_diff 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_diff, this is the rule to start with:

vcs_diff Allowed

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

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

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

FAQ

Questions about vcs_diff

What does the vcs_diff tool do? +

What parameters does vcs_diff accept? +

vcs_diff accepts 2 parameters: path, staged. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on vcs_diff? +

Register the Breakpoint MCP server in PolicyLayer and add a rule for vcs_diff: 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.

What risk level is vcs_diff? +

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

Can I rate-limit vcs_diff? +

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

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

vcs_diff 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.

KEEP EXPLORING

More on Breakpoint, and thousands of servers like it.

This server

All 280 Breakpoint tools →

Across the catalogue

binary_diff on 010 Editor → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →