apply_changes · Git Polite MCP: Risk & Policy

WHAT IT DOES

What apply_changes does on Git Polite

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

WHY IT NEEDS A POLICY

Why apply_changes needs a policy

Apply_changes on a Git server performs write operations by modifying the staging area or applying diffs to tracked files. This is reversible (changes can be unstaged or reverted), so it is Write rather than Destructive. Severity is high because an AI agent could inadvertently apply unintended changes to a codebase.

From the tool's definition Tool name is 'apply_changes' on a Git server that 'organizes Git changes into clean, focused commits.' The sibling tools (auto_commit, diff, list_changes, unstack) indicate this server manipulates Git state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

apply_changes Rate-limited

apply_changes 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": {
    "apply_changes": {
      "limits": [
        {
          "counter": "apply_changes_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 Polite, so you can run agents against it safely.

FAQ

Questions about apply_changes

What does the apply_changes tool do? +

apply_changes. It is categorised as a Write tool in the Git Polite MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on apply_changes? +

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

What risk level is apply_changes? +

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

Can I rate-limit apply_changes? +

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

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

apply_changes is provided by the Git Polite MCP server (uneco/mcp-git-polite). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.