gitlab_list_branches

List repository branches

SERVERSage MCP SOURCEsagemcp/sagemcp

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/sagemcp-sagemcp/gitlab-list-branches.md

WHAT IT DOES

What gitlab_list_branches does on Sage MCP

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

RISK

Why gitlab_list_branches is rated Low

This tool performs a read-only operation that retrieves a list of branches from a GitLab repository. It has no capability to create, modify, delete, or execute anything. The blast radius of misuse is minimal—an attacker could only enumerate branches, which is typically non-sensitive metadata. The low severity reflects the informational nature of the data retrieved.

From the tool's definition Tool name is 'gitlab_list_branches' and description states 'List repository branches' — a query operation that retrieves data without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs gitlab_list_branches safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gitlab_list_branches, this is the rule to start with:

gitlab_list_branches Allowed

gitlab_list_branches is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gitlab_list_branches": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sage MCP, apply this rule, and every gitlab_list_branches call is checked against it from then on.

FAQ

Questions about gitlab_list_branches

What does the gitlab_list_branches tool do? +

List repository branches. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on gitlab_list_branches? +

Register the Sage 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 Sage MCP. 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 Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sage, and thousands of servers like it.

This server

All 359 Sage tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →