vcs_status

SERVERBreakpoint SOURCEbreakpoint-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/breakpoint-mcp/vcs-status.md

WHAT IT DOES

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.

RISK

Why vcs_status is rated Low

This tool queries and retrieves git repository metadata and working tree status. It has no capability to modify, execute, or delete data. The explicit 'Read-only' designation and passive reporting nature confirm this is a safe data retrieval operation with no side effects.

From the tool's definition Tool name 'vcs_status' and description explicitly states 'Read-only' and 'Reports' git repository status; retrieves information about current branch, file staging state, and upstream tracking without modifying any data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Allowed

vcs_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "vcs_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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.

FAQ

Questions about vcs_status

What does the vcs_status tool do? +

Working-tree status of the project's git repository: current branch, upstream ahead/behind, and the staged / unstaged / untracked / unmerged file lists. Read-only. Reports clean=true when nothing is pending. 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.

How do I enforce a policy on vcs_status? +

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.

What risk level is vcs_status? +

vcs_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit vcs_status? +

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.

How do I block vcs_status completely? +

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.

What MCP server provides vcs_status? +

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.

KEEP EXPLORING

More on Breakpoint, and thousands of servers like it.

This server

All 274 Breakpoint tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →