git_push

A execute tool on the GitHub MCP server.

SERVERGitHub SOURCEoci:ghcr.io/aifity/omnigit-mcp:0.5.0

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-aifity-omnigit-mcp/git-push.md

WHAT IT DOES

What git_push does on GitHub

AI agents invoke git_push to trigger actions in GitHub. 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.

RISK

Why git_push is rated High

A git push sends commits to a remote repository, potentially overwriting remote branches or publishing unintended code. While it can be partially reversed, a forced push can be destructive and it triggers external operations on remote infrastructure. The description is minimal but the operation is well-understood.

From the tool's definition Tool name 'git_push' and description 'Git push' — pushes local commits to a remote repository

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs git_push safely

PolicyLayer is an MCP gateway: it sits between your AI agents and GitHub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For git_push, this is the rule to start with:

git_push Rate-limited

git_push 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": {
    "git_push": {
      "limits": [
        {
          "counter": "git_push_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every git_push call is checked against it from then on.

FAQ

Questions about git_push

What does the git_push tool do? +

git_push is a execute tool on the GitHub MCP server. It is categorised as a Execute tool in the GitHub MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on git_push? +

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

What risk level is git_push? +

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

Can I rate-limit git_push? +

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

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

git_push is provided by the GitHub MCP server (oci:ghcr.io/aifity/omnigit-mcp:0.5.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on GitHub, and thousands of servers like it.

This server

All 245 GitHub tools → High-risk tools on this server →

Across the catalogue

deploy_git_repo on cPanel MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →