vcs_restore
Discard uncommitted working-tree changes to the given paths, restoring them from the index/HEAD (git restore -- <paths>). DESTRUCTIVE — the discarded edits are unrecoverable — so it is elicitation-gated: pass confirm:true to bypass the prompt on clients that can't elicit. restored is MEASURED, no...
This record as markdown: /tools/breakpoint-mcp/vcs-restore.md
What vcs_restore does on Breakpoint
AI agents use vcs_restore to create or update resources in Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Breakpoint environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
paths | array | Yes | Paths to discard changes for (res:// or project-relative) |
confirm | boolean | — | Skip the confirmation prompt |
Parameters from the server's own tool schema.
Why vcs_restore is rated Medium
An AI agent can call vcs_restore faster than any human can review: one bad instruction and it creates or modifies resources in Breakpoint by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs vcs_restore 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_restore, this is the rule to start with:
vcs_restore stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_restore call is checked against it from then on.
Questions about vcs_restore
Discard uncommitted working-tree changes to the given paths, restoring them from the index/HEAD (git restore -- <paths>). DESTRUCTIVE — the discarded edits are unrecoverable — so it is elicitation-gated: pass confirm:true to bypass the prompt on clients that can't elicit. restored is MEASURED, not echoed: it lists only the paths git actually changed, so a path with nothing to discard is absent from it rather than reported as discarded work. requested carries what you asked for, and stranded names any path still dirty afterwards (a partial, not an error). It is categorised as a Write tool in the Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
vcs_restore accepts 2 parameters: paths, confirm. Required: paths. 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_restore: 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_restore is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the vcs_restore 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_restore. 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_restore 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