push_changes · Git MCP Assistant Tool MCP: Risk & Policy

WHAT IT DOES

What push_changes does on Git MCP Assistant Tool

AI agents invoke push_changes to trigger actions in Git MCP Assistant Tool. 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 push_changes needs a policy

Pushing changes to a remote repository triggers an external operation that modifies the state of a remote system. While not locally destructive, a push can overwrite remote history (especially with force-push), expose sensitive code, or corrupt shared branches.

From the tool's definition Push changes to remote repository

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

push_changes Rate-limited

push_changes 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": {
    "push_changes": {
      "limits": [
        {
          "counter": "push_changes_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 Git MCP Assistant Tool, so you can run agents against it safely.

FAQ

Questions about push_changes

What does the push_changes tool do? +

Push changes to remote repository. It is categorised as a Execute tool in the Git MCP Assistant Tool MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on push_changes? +

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

What risk level is push_changes? +

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

Can I rate-limit push_changes? +

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

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

push_changes is provided by the Git MCP Assistant Tool MCP server (kamiwaza-drew/tool-git). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.