list_branches
AI agents call list_branches to retrieve information from GitBranchMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or lists branch information with no side effects. It does not create, modify, delete, or execute operations—it merely queries state. The severity is low because misuse would at most expose branch names and metadata, with no destructive or operational impact.
From the tool's definition Tool name 'list_branches' indicates a query/retrieval operation that enumerates existing branches without modification. No description provided, but the name and sibling tool patterns (create_branch, delete_branch, export_*) confirm this is a read operation.
Attacks that exploit this kind of access
list_branches. It is categorised as a Read tool in the GitBranchMCP MCP Server, which means it retrieves data without modifying state.
Register the GitBranch 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 GitBranchMCP. 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 GitBranch MCP server (lianggaoyuan/gitbranchmcp). 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 →