git_status

Show current git status of HA config directory.

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-status.md

WHAT IT DOES

What git_status does on Ha Nexus Agent

AI agents call git_status 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_status is rated Low

This tool only reads and displays the current state of a git repository (staged changes, unstaged changes, branch info, etc.). It performs no side effects, does not execute commands that modify files or trigger external operations, and does not access sensitive data beyond what is already accessible via the local filesystem. The blast radius of misuse is minimal—an agent could only see local git status information.

From the tool's definition Tool name 'git_status' and description 'Show current git status of HA config directory' indicate a query operation that retrieves git repository status information without modifying anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs git_status 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_status, this is the rule to start with:

git_status Allowed

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

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_status call is checked against it from then on.

FAQ

Questions about git_status

What does the git_status tool do? +

Show current git status of HA config directory. 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_status? +

Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for git_status: 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_status? +

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

Can I rate-limit git_status? +

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

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

git_status 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

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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