repo_commit · Git Steer MCP: Risk & Policy

WHAT IT DOES

What repo_commit does on Git Steer

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

WHY IT NEEDS A POLICY

Why repo_commit needs a policy

This tool creates or modifies data (repository commits) in a reversible manner—commits can be reverted or amended. It does not permanently delete data (thus not Destructive), nor does it execute arbitrary code or trigger external operations (thus not Execute). While committing malicious code could have downstream Execute-like effects, the tool itself performs a Write action.

From the tool's definition Tool description explicitly states 'Commit files directly to a repository' and 'Supports multiple files in a single commit.' The verb 'commit' is a write operation that modifies repository state by adding/changing tracked files.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

repo_commit Rate-limited

repo_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": {
    "repo_commit": {
      "limits": [
        {
          "counter": "repo_commit_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Git Steer, so you can run agents against it safely.

FAQ

Questions about repo_commit

What does the repo_commit tool do? +

Commit files directly to a repository via GitHub API (no local clone needed). Supports multiple files in a single commit. It is categorised as a Write tool in the Git Steer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on repo_commit? +

Register the Git Steer MCP server in PolicyLayer and add a rule for repo_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 Git Steer. Nothing to install.

What risk level is repo_commit? +

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

Can I rate-limit repo_commit? +

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

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

repo_commit is provided by the Git Steer MCP server (ry-ops/git-steer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.