git_pull · MCP Git Server MCP: Risk & Policy

WHAT IT DOES

What git_pull does on MCP Git Server

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

WHY IT NEEDS A POLICY

Why git_pull needs a policy

git_pull fetches and merges changes from a remote repository into the local branch. This modifies local files and history (a Write operation). While it can cause merge conflicts or overwrite local changes, it is generally reversible (via reset/revert), so it does not rise to Destructive. Misuse could overwrite local work or introduce unwanted changes, hence medium severity.

From the tool's definition Pull changes from remote repository

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git_pull Rate-limited

git_pull 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_pull": {
      "limits": [
        {
          "counter": "git_pull_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 MCP Git Server, so you can run agents against it safely.

FAQ

Questions about git_pull

What does the git_pull tool do? +

Pull changes from remote repository. It is categorised as a Write tool in the MCP Git 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_pull? +

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

What risk level is git_pull? +

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

Can I rate-limit git_pull? +

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

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

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