github.branches

Branches of a repository: name, head commit sha, and protection flag. Read-only; no caller key needed.

SERVERMcp SOURCE@2sio/mcp

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/io-github-2s-io-mcp/github.branches.md

WHAT IT DOES

What github.branches does on Mcp

AI agents call github.branches to retrieve information from 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 github.branches is rated Low

This tool queries and returns information about git repository branches without modifying any data, executing code, or triggering external operations. It is purely informational, making it a Read category tool with low severity due to the non-sensitive nature of publicly retrievable repository metadata.

From the tool's definition Tool description states 'Branches of a repository: name, head commit sha, and protection flag. Read-only; no caller key needed.' The 'read-only' designation and retrieval of repository metadata (branch names, commit SHAs, protection status) confirm this is a…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs github.branches safely

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

github.branches Allowed

github.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": {
    "github.branches": {}
  }
}

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

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

FAQ

Questions about github.branches

What does the github.branches tool do? +

Branches of a repository: name, head commit sha, and protection flag. Read-only; no caller key needed. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on github.branches? +

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

What risk level is github.branches? +

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

Can I rate-limit github.branches? +

Yes. Add a rate_limit block to the github.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 github.branches completely? +

Set action: deny in the PolicyLayer policy for github.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 github.branches? +

github.branches is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 572 tools →

Across the catalogue

The MCP Attack Database →

Guides

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