git_commit_all

Stage all changes and commit them with a message. Use before making risky changes as a checkpoint.

SERVERHa Nexus Agent SOURCEfistacho/ha-nexus-agent
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/fistacho-ha-nexus-agent/git-commit-all.md

What git_commit_all does on Ha Nexus Agent

AI agents invoke git_commit_all to trigger actions in Ha Nexus Agent. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why git_commit_all is rated High

This tool executes a git commit operation, which runs external VCS commands and modifies the git history. While commits are technically reversible (via revert/reset), the act of staging all changes indiscriminately and committing them is an active execution of a multi-step external operation.

From the tool's definition 'Stage all changes and commit them with a message' — triggers a git staging and commit operation on the filesystem

Risk signalsBulk/mass operation — affects multiple targets

Questions about git_commit_all

What does the git_commit_all tool do? +

Stage all changes and commit them with a message. Use before making risky changes as a checkpoint. It is categorised as a Execute tool in the Ha Nexus Agent MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on git_commit_all? +

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

git_commit_all is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit git_commit_all? +

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

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

git_commit_all 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.

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Ha Nexus Agent's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.