vcs_branch_list
List branches with their short object name and a flag for the current branch. Local only by default; set remotes=true to include remote-tracking branches. Read-only.
This record as markdown: /tools/breakpoint-mcp/vcs-branch-list.md
What vcs_branch_list does on Breakpoint
AI agents call vcs_branch_list 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 |
|---|---|---|---|
remotes | boolean | — | Include remote-tracking branches (default false) |
Parameters from the server's own tool schema.
Why vcs_branch_list is rated Low
This tool retrieves version control branch information without modifying, executing, or deleting any data. It is a pure read operation analogous to 'git branch' command, presenting no risk of data corruption or unintended state changes.
From the tool's definition Tool description explicitly states 'Read-only' and 'List branches' — a query operation with no side effects. Returns branch metadata (short object name, current branch flag) with optional inclusion of remote-tracking branches via remotes parameter.
Attacks that exploit this kind of access
The rule that runs vcs_branch_list 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_branch_list, this is the rule to start with:
vcs_branch_list 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_branch_list call is checked against it from then on.
Questions about vcs_branch_list
List branches with their short object name and a flag for the current branch. Local only by default; set remotes=true to include remote-tracking branches. Read-only. It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.
vcs_branch_list accepts 1 parameter: remotes. 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_branch_list: 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_branch_list 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_branch_list 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_branch_list. 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_branch_list 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