git_pull · Context MCP: Risk & Policy

WHAT IT DOES

What git_pull does on Context

AI agents invoke git_pull to trigger actions in Context. 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_pull needs a policy

git pull fetches remote changes and merges them into the working branch, which is an external operation with real side effects: it modifies local files, potentially causes merge conflicts, and changes the state of the repository. It is not a simple read and not necessarily destructive (though it can overwrite local changes), making Execute the most appropriate category.

From the tool's definition Pull from remote and merge into current branch

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git_pull Rate-limited

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

FAQ

Questions about git_pull

What does the git_pull tool do? +

Pull from remote and merge into current branch. It is categorised as a Execute tool in the Context 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_pull? +

Register the Context 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 Context. Nothing to install.

What risk level is git_pull? +

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

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 Context MCP server (vibhasdutta/context-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.