Low Risk

list_branches

列出 Gitee 仓库中的分支

How to control list_branches ↓

What list_branches does on Gitee

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

Low Risk

Why list_branches needs a policy

This tool queries and retrieves branch information from a Gitee repository. It performs a read-only operation with no side effects, no data modification, no code execution, and no destructive actions. The blast radius of misuse is minimal—an agent could only enumerate branches, which is informational only.

From the tool's definition Tool name 'list_branches' and description '列出 Gitee 仓库中的分支' (list branches in Gitee repository) indicate retrieval of repository metadata without modification or execution of external operations.

Documented attack patterns abuse exactly the kind of access list_branches gives an agent:

How to control list_branches

PolicyLayer is an MCP gateway — it sits between your AI agents and Gitee, and nothing reaches the server without passing your rules. This is the rule we recommend for list_branches:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_branches": {}
  }
}

list_branches is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Gitee — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about list_branches

What does the list_branches tool do? +

列出 Gitee 仓库中的分支. It is categorised as a Read tool in the Gitee MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_branches? +

Register the Gitee 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 Gitee. Nothing to install.

What risk level is list_branches? +

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

Can I rate-limit list_branches? +

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.

How do I block list_branches completely? +

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.

What MCP server provides list_branches? +

list_branches is provided by the Gitee MCP server (normal-coder/gitee-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Gitee tool call.

Start from Gitee, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

20 Gitee tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.