git_list_branches

List all local branches in HA config repo.

SERVERHa Nexus Agent SOURCEfistacho/ha-nexus-agent

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/fistacho-ha-nexus-agent/git-list-branches.md

WHAT IT DOES

What git_list_branches does on Ha Nexus Agent

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

RISK

Why git_list_branches is rated Low

This tool only lists existing git branches—a read-only operation with no side effects. It retrieves data about the repository state without creating, modifying, deleting, or executing anything. The blast radius of misuse is minimal; an attacker gains only visibility into branch names.

From the tool's definition Tool name 'git_list_branches' and description 'List all local branches in HA config repo' indicate a query operation that retrieves branch information without modifying or executing any code.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs git_list_branches safely

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

git_list_branches Allowed

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

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

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

FAQ

Questions about git_list_branches

What does the git_list_branches tool do? +

List all local branches in HA config repo. It is categorised as a Read tool in the Ha Nexus Agent MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on git_list_branches? +

Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for git_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 Ha Nexus Agent. Nothing to install.

What risk level is git_list_branches? +

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

Can I rate-limit git_list_branches? +

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

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

git_list_branches is provided by the Ha Nexus Agent MCP server (fistacho/ha-nexus-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ha Nexus Agent, and thousands of servers like it.

This server

All 276 Ha Nexus Agent tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →claude_git_status on Claude Bridge →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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