git_commit_feature · AutoDev MCP: Risk & Policy

WHAT IT DOES

What git_commit_feature does on AutoDev MCP

AI agents invoke git_commit_feature to trigger actions in AutoDev MCP. 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 IT NEEDS A POLICY

Why git_commit_feature needs a policy

Creating a git commit is an external operation that modifies the repository's version history. While not purely destructive (commits can technically be reverted), it executes a side-effecting Git operation whose impact depends on what was staged/committed. It falls under Execute as it triggers an external VCS operation.

From the tool's definition "create a git commit according to configured policy" — triggers an external Git operation that modifies repository history

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git_commit_feature Rate-limited

git_commit_feature stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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_feature": {
      "limits": [
        {
          "counter": "git_commit_feature_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about git_commit_feature

What does the git_commit_feature tool do? +

When a complete small feature is done and tests pass, create a git commit according to configured policy. It is categorised as a Execute tool in the AutoDev MCP 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_feature? +

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

What risk level is git_commit_feature? +

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

Can I rate-limit git_commit_feature? +

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

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

git_commit_feature is provided by the AutoDev MCP server (rookiejefren/autocoding-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.