vcs_status
Working-tree status of the project's git repository, every path project-relative. Changes elsewhere in the repository are listed separately in outside_project. Read-only; errors clearly if the project path is not a git work tree.
This record as markdown: /tools/breakpoint-mcp/vcs-status.md
What vcs_status does on Breakpoint
AI agents call vcs_status 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.
Why vcs_status is rated Low
Even though vcs_status 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 signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs vcs_status 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_status, this is the rule to start with:
vcs_status 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_status call is checked against it from then on.
Questions about vcs_status
Working-tree status of the project's git repository, every path project-relative. Changes elsewhere in the repository are listed separately in outside_project. Read-only; errors clearly if the project path is not a git work tree. It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.
Register the Breakpoint MCP server in PolicyLayer and add a rule for vcs_status: 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_status 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_status 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_status. 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_status 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