mcp_git_commit · Local Code MCP: Risk & Policy

WHAT IT DOES

What mcp_git_commit does on Local Code

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

WHY IT NEEDS A POLICY

Why mcp_git_commit needs a policy

Git commits are write operations that create permanent records in the repository history. However, the tool is constrained to already-staged changes (not arbitrary modifications), operates within allowed folders per the server's safe design, and commits themselves are reversible through git revert/reset. This makes it Write rather than Destructive.

From the tool's definition Tool description states 'Create a git commit from already staged changes.' The verb 'Create' indicates a write operation that modifies version control state irreversibly by recording committed changes.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mcp_git_commit Rate-limited

mcp_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": {
    "mcp_git_commit": {
      "limits": [
        {
          "counter": "mcp_git_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 Local Code, so you can run agents against it safely.

FAQ

Questions about mcp_git_commit

What does the mcp_git_commit tool do? +

Create a git commit from already staged changes. It is categorised as a Write tool in the Local Code MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on mcp_git_commit? +

Register the Local Code MCP server in PolicyLayer and add a rule for mcp_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 Local Code. Nothing to install.

What risk level is mcp_git_commit? +

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

Can I rate-limit mcp_git_commit? +

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

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

mcp_git_commit is provided by the Local Code MCP server (js190-prog/local-code-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.