git_remotes · Git MCP: Risk & Policy

WHAT IT DOES

What git_remotes does on Git

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

This tool can push to and pull from remote repositories, which are external network operations. Pushing can overwrite remote history and affects other collaborators; pulling modifies local state. These are side-effecting operations beyond simple reads, and push in particular can be destructive if misused (e.g., force-push).

From the tool's definition 'fetch|pull|push for network/transport operations' — push and pull perform external network operations that modify remote repository state

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git_remotes Rate-limited

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

FAQ

Questions about git_remotes

What does the git_remotes tool do? +

Remote tool. Use action=list|manage|fetch|pull|push for network/transport operations. It is categorised as a Execute tool in the Git 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_remotes? +

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

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

Can I rate-limit git_remotes? +

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

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

git_remotes 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.