vcs_add
Stage changes for the next commit. With paths, stages exactly those (res:// or repo-relative); omit paths to stage everything (git add -A). Returns the resulting staged file list. Reversible with vcs_restore-staged / git restore --staged, so not gated.
This record as markdown: /tools/breakpoint-mcp/vcs-add.md
What vcs_add does on Breakpoint
AI agents use vcs_add 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 | — | Paths to stage (res:// or repo-relative). Omit to stage all. |
Parameters from the server's own tool schema.
Why vcs_add is rated Medium
This tool modifies the state of the repository by staging changes, which is a write operation. However, because the action is explicitly reversible (as confirmed by the vcs_restore-staged capability), it does not qualify as Destructive.
From the tool's definition Tool description states it 'Stage[s] changes for the next commit' and is 'Reversible with vcs_restore-staged / git restore --staged'. This modifies the git staging area but does not irreversibly delete or overwrite data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs vcs_add 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_add, this is the rule to start with:
vcs_add 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_add call is checked against it from then on.
Questions about vcs_add
Stage changes for the next commit. With paths, stages exactly those (res:// or repo-relative); omit paths to stage everything (git add -A). Returns the resulting staged file list. Reversible with vcs_restore-staged / git restore --staged, so not gated. 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_add accepts 1 parameter: 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_add: 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_add 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_add 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_add. 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_add 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