List all branches in the repository with current branch highlighted
AI agents call list_branches to retrieve information from Git Helper MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays git repository metadata (branch names and current branch state) without creating, modifying, deleting, or executing any operations. It is a pure read operation with no blast radius if misused by an AI agent—the worst outcome would be disclosure of branch names already visible to the user.
From the tool's definition Tool name 'list_branches' and description 'List all branches in the repository' indicate a query operation that retrieves branch information with no modification or side effects.
Attacks that exploit this kind of access
List all branches in the repository with current branch highlighted. It is categorised as a Read tool in the Git Helper MCP MCP Server, which means it retrieves data without modifying state.
Register the Git Helper MCP server in PolicyLayer and add a rule for list_branches: 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 Git Helper MCP. Nothing to install.
list_branches 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 list_branches 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 list_branches. 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.
list_branches is provided by the Git Helper MCP server (letscodethebrain/git-helper-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →