vcs_switch
Switch to an existing branch (git switch <branch>). No --force: if local changes would be overwritten, git refuses and its message is returned unchanged — nothing is clobbered — so this is not gated.
This record as markdown: /tools/breakpoint-mcp/vcs-switch.md
What vcs_switch does on Breakpoint
AI agents invoke vcs_switch to trigger actions in Breakpoint. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
branch | string | Yes | Existing branch to switch to |
Parameters from the server's own tool schema.
Why vcs_switch is rated High
The tool executes a git switch command, which changes the current branch and updates the working directory. While it explicitly notes it won't overwrite local changes (no --force), it still triggers an external git operation that modifies repository state (HEAD pointer, working tree). This qualifies as Execute since it runs an external operation whose effects depend on the branch argument provided.
From the tool's definition Switch to an existing branch (`git switch <branch>`) — runs a git command that changes the working tree state
Attacks that exploit this kind of access
The rule that runs vcs_switch 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_switch, this is the rule to start with:
vcs_switch stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_switch call is checked against it from then on.
Questions about vcs_switch
Switch to an existing branch (git switch <branch>). No --force: if local changes would be overwritten, git refuses and its message is returned unchanged — nothing is clobbered — so this is not gated. It is categorised as a Execute tool in the Breakpoint MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
vcs_switch accepts 1 parameter: branch. Required: branch. 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_switch: 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_switch is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the vcs_switch 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_switch. 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_switch 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.
Across the catalogue