List all Git branches in a repository. Returns branch names and metadata (current branch, commit info). Use this to see available branches before switching or comparing versions. Pass either the id or name from openl_list_repositories() — both are accepted (case-insensitive). Do not invent exampl...
AI agents call list_branches to retrieve information from Openl without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query operation that retrieves and displays Git branch metadata (branch names, current branch, commit info) without creating, modifying, or deleting any data. It has no side effects and is used for information gathering before other operations. The blast radius of misuse is minimal—worst case, an agent lists available branches unnecessarily.
From the tool's definition Tool description explicitly states 'List all Git branches in a repository. Returns branch names and metadata' - listing and returning information with no modification capability.
Attacks that exploit this kind of access
List all Git branches in a repository. Returns branch names and metadata (current branch, commit info). Use this to see available branches before switching or comparing versions. Pass either the id or name from openl_list_repositories() — both are accepted (case-insensitive). Do not invent example values; call openl_list_repositories() first if not in context. It is categorised as a Read tool in the Openl MCP Server, which means it retrieves data without modifying state.
Register the Openl 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 Openl. 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 Openl MCP server (openl-mcp-server). 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 →