commit_manager_work

THE RISK

Medium Risk

Why commit_manager_work needs a policy

This tool creates git commits, which is a Write operation as it modifies repository state. While commits are technically reversible (via revert/reset), they represent permanent additions to history and alter the repository's state.

From the tool's definition 'Commit current work with proper git practices' indicates the tool modifies a git repository by creating a commit, which is a reversible write operation.

Documented attack patterns abuse exactly the kind of access commit_manager_work gives an agent:

POLICY

How to control commit_manager_work

PolicyLayer is an MCP gateway — it sits between your AI agents and tmux-claude MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for commit_manager_work:

policy.json

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

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

Create a free account and register tmux-claude MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More tmux-claude MCP Server tools

Destructive terminate Terminate a Claude instance and optionally its children Destructive vm_terminate Terminate a VM instance (permanent destruction) Execute executeParallel Execute multiple tasks in parallel using Specialist instances (Manager only) Execute restart Restart a dead instance using --continue flag Execute vm_start Start a stopped VM instance Execute vm_stop Stop a running VM instance Execute distributeWork Distribute tasks across multiple Managers (Executive only) Execute enhancedSend Send a message with queuing and guaranteed delivery

All 26 tmux-claude MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about commit_manager_work

What does the commit_manager_work tool do? +

Commit current work with proper git practices (Manager only). It is categorised as a Write tool in the tmux-claude MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on commit_manager_work? +

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

What risk level is commit_manager_work? +

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

Can I rate-limit commit_manager_work? +

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

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

commit_manager_work is provided by the tmux-claude MCP Server MCP server (michael-abdo/tmux-claude-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every tmux-claude MCP Server tool call.

Start from tmux-claude MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →