git_commit

Commit changes in the workspace. Only available when working in an isolated worktree branch. Stages all changes and commits with the given message.

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cowork-os/git-commit.md

WHAT IT DOES

What git_commit does on CoWork OS

AI agents use git_commit to create or update resources in CoWork OS, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CoWork OS environment.

RISK

Why git_commit is rated Medium

The git_commit tool modifies the repository state by creating a new commit object and advancing the branch reference. While commits are persisted, they are not irreversible - they can be undone via revert, reset, or amend operations. The tool operates only in an 'isolated worktree branch', which further limits unintended impact. This qualifies as Write rather than Destructive.

From the tool's definition Tool description states it 'Stages all changes and commits with the given message' - commits are write operations that create new versions in the git history.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs git_commit safely

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

git_commit Rate-limited

git_commit stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "git_commit": {
      "limits": [
        {
          "counter": "git_commit_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about git_commit

What does the git_commit tool do? +

Commit changes in the workspace. Only available when working in an isolated worktree branch. Stages all changes and commits with the given message. It is categorised as a Write tool in the CoWork OS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on git_commit? +

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

What risk level is git_commit? +

git_commit is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit git_commit? +

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

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

git_commit is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CoWork OS, and thousands of servers like it.

This server

All 342 CoWork OS tools →

Across the catalogue

generate_commit on MCP Server PR Pilot → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →