from_branch

Source branch (defaults to repo default) (string, optional)

SERVERGitHub SOURCEoci:ghcr.io/aifity/omnigit-mcp:0.5.0

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-aifity-omnigit-mcp/from-branch.md

WHAT IT DOES

What from_branch does on GitHub

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

RISK

Why from_branch is rated Low

This tool/parameter merely specifies which branch to read from; it has no side effects on the repository. It is informational input for queries rather than an action that modifies or executes code. The default fallback behavior further suggests it is a passive parameter for read operations.

From the tool's definition Tool name 'from_branch' and description 'Source branch (defaults to repo default)' indicate this is a parameter for specifying a source branch, likely used in read operations like comparing branches or fetching branch information.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs from_branch safely

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

from_branch Allowed

from_branch 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": {
    "from_branch": {}
  }
}

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

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

FAQ

Questions about from_branch

What does the from_branch tool do? +

Source branch (defaults to repo default) (string, optional). It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on from_branch? +

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

What risk level is from_branch? +

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

Can I rate-limit from_branch? +

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

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

from_branch is provided by the GitHub MCP server (oci:ghcr.io/aifity/omnigit-mcp:0.5.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on GitHub, and thousands of servers like it.

This server

All 245 GitHub tools →

Across the catalogue

extract_text_from_image on Percepta MCP Server → The MCP Attack Database →

Guides

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