git_set_upstream · Git MCP: Risk & Policy

WHAT IT DOES

What git_set_upstream does on Git

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

WHY IT NEEDS A POLICY

Why git_set_upstream needs a policy

Setting an upstream branch modifies git configuration reversibly—the tracking relationship can be changed or removed without data loss. This is a write operation rather than execute because it configures a relationship rather than running arbitrary commands.

From the tool's definition Tool name 'git_set_upstream' and description 'Set the upstream tracking branch for a local branch' indicate modification of branch configuration metadata.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git_set_upstream Rate-limited

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

FAQ

Questions about git_set_upstream

What does the git_set_upstream tool do? +

Set the upstream tracking branch for a local branch. It is categorised as a Write tool in the Git MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on git_set_upstream? +

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

What risk level is git_set_upstream? +

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

Can I rate-limit git_set_upstream? +

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

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

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