github_push_feature_branch · Github MCP: Risk & Policy

WHAT IT DOES

What github_push_feature_branch does on Github

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

WHY IT NEEDS A POLICY

Why github_push_feature_branch needs a policy

This tool writes to a Git repository by pushing local commits to a remote feature branch and configuring upstream tracking. While the operation modifies repository state, it is scoped to non-protected branches only, is reversible (commits can be amended or reverted), and poses no destructive risk.

From the tool's definition Tool performs 'Push a non-protected feature branch and set upstream' — creates/modifies remote Git state by pushing commits to a feature branch, which is a reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

github_push_feature_branch Rate-limited

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

FAQ

Questions about github_push_feature_branch

What does the github_push_feature_branch tool do? +

Push a non-protected feature branch and set upstream. Refuses main/master. It is categorised as a Write tool in the Github MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on github_push_feature_branch? +

Register the Github MCP server in PolicyLayer and add a rule for github_push_feature_branch: 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 github_push_feature_branch? +

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

Can I rate-limit github_push_feature_branch? +

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

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

github_push_feature_branch is provided by the Github MCP server (matiasnjacob/github-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.