push_git_tag · Git MCP: Risk & Policy

WHAT IT DOES

What push_git_tag does on Git MCP

AI agents invoke push_git_tag to trigger actions in Git 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 push_git_tag needs a policy

Pushing a git tag to a remote repository is an external operation that modifies the remote repository state. While not strictly destructive (tags can be deleted), pushing tags is an irreversible network operation that affects shared infrastructure and can trigger CI/CD pipelines, release workflows, or other automated systems.

From the tool's definition Push a git tag to the default remote

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

push_git_tag Rate-limited

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

FAQ

Questions about push_git_tag

What does the push_git_tag tool do? +

Push a git tag to the default remote. It is categorised as a Execute tool in the Git 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 push_git_tag? +

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

What risk level is push_git_tag? +

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

Can I rate-limit push_git_tag? +

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

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

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