git_apply_patch · LocalAnt MCP: Risk & Policy

WHAT IT DOES

What git_apply_patch does on LocalAnt

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

WHY IT NEEDS A POLICY

Why git_apply_patch needs a policy

Applying a patch modifies repository files and state through git, which is a write operation that changes data. It is reversible (git operations can be undone), so it does not qualify as Destructive. The severity is medium because an attacker could inject malicious code changes into a repository, but the dry-run check provides some safety guardrail.

From the tool's definition Tool applies a unified diff to a repository using git apply. The description explicitly mentions applying changes to a repo, which modifies files and commits state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git_apply_patch Rate-limited

git_apply_patch 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_apply_patch": {
      "limits": [
        {
          "counter": "git_apply_patch_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 LocalAnt, so you can run agents against it safely.

FAQ

Questions about git_apply_patch

What does the git_apply_patch tool do? +

Apply a unified diff to the repo (git apply, with a dry-run check first). It is categorised as a Write tool in the LocalAnt 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_apply_patch? +

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

What risk level is git_apply_patch? +

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

Can I rate-limit git_apply_patch? +

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

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

git_apply_patch is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.