vcs_log
Recent commits, newest first: full and short hash, author, ISO author date, and subject. Optionally limit to commits touching a path (accepts res:// or repo-relative). Read-only.
This record as markdown: /tools/breakpoint-mcp/vcs-log.md
What vcs_log does on Breakpoint
AI agents call vcs_log 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 |
|---|---|---|---|
path | string | — | Only commits touching this path (res:// or repo-relative) |
max_count | integer | — | Max commits to return (default 20) |
Parameters from the server's own tool schema.
Why vcs_log is rated Low
This tool queries and retrieves version control system commit history data without side effects. The explicit 'Read-only' designation confirms it performs data retrieval only, making it a Read category tool with low severity since it cannot modify, delete, or execute operations.
From the tool's definition Tool description explicitly states 'Read-only' and retrieves 'Recent commits, newest first: full and short hash, author, ISO author date, and subject' without any modification or execution capabilities.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs vcs_log 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_log, this is the rule to start with:
vcs_log 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_log call is checked against it from then on.
Questions about vcs_log
Recent commits, newest first: full and short hash, author, ISO author date, and subject. Optionally limit to commits touching a path (accepts res:// or repo-relative). Read-only. It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.
vcs_log accepts 2 parameters: path, max_count. 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_log: 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_log 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_log 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_log. 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_log 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