New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

gitlab_list_branches

List all branches in a project with protection status and last commit info.

SERVERGitlab SOURCEdkeeno/gitlab-mcp-server
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/dkeeno-gitlab-mcp-server/gitlab-list-branches.md

What gitlab_list_branches does on Gitlab

AI agents call gitlab_list_branches to retrieve information from Gitlab without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why gitlab_list_branches is rated Low

This tool performs a straightforward data retrieval operation—listing branches and their metadata. It has no side effects, does not execute code, does not modify state, and does not delete or move resources. The blast radius of misuse is minimal; an agent could at worst enumerate repository structure information that is typically already visible to authorized users. It cleanly fits the 'Read' category as defined.

From the tool's definition Tool name 'gitlab_list_branches' and description 'List all branches in a project with protection status and last commit info' indicate a read-only operation that retrieves and queries branch data without modifying or executing anything.

Questions about gitlab_list_branches

What does the gitlab_list_branches tool do? +

List all branches in a project with protection status and last commit info. It is categorised as a Read tool in the Gitlab MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on gitlab_list_branches? +

Register the Gitlab MCP server in PolicyLayer and add a rule for gitlab_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 Gitlab. Nothing to install.

What risk level is gitlab_list_branches? +

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

Can I rate-limit gitlab_list_branches? +

Yes. Add a rate_limit block to the gitlab_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.

How do I block gitlab_list_branches completely? +

Set action: deny in the PolicyLayer policy for gitlab_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.

What MCP server provides gitlab_list_branches? +

gitlab_list_branches is provided by the Gitlab MCP server (dkeeno/gitlab-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Gitlab, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Gitlab's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.