git_remote_add · GitHub MCP Server MCP: Risk & Policy

WHAT IT DOES

What git_remote_add does on GitHub MCP Server

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

WHY IT NEEDS A POLICY

Why git_remote_add needs a policy

This tool creates a new remote reference in a Git repository, modifying repository configuration. While reversible via git_remote_remove, it represents a Write operation that alters repository state. Severity is medium because misconfiguration could disrupt collaboration workflows, but it doesn't execute code, delete data, or cause financial impact.

From the tool's definition Tool name 'git_remote_add' and description 'Adds a remote repository' indicate creation/modification of Git configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git_remote_add Rate-limited

git_remote_add 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_remote_add": {
      "limits": [
        {
          "counter": "git_remote_add_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 MCP Server, so you can run agents against it safely.

FAQ

Questions about git_remote_add

What does the git_remote_add tool do? +

Adds a remote repository. It is categorised as a Write tool in the GitHub MCP Server 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_remote_add? +

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

What risk level is git_remote_add? +

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

Can I rate-limit git_remote_add? +

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

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

git_remote_add is provided by the GitHub MCP Server MCP server (0xshariq/github-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

git_remote_add is one line of GitHub MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →