git_pull

Pull changes from remote

SERVERCode MCP Server SOURCEagentics-ai/code-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/agentics-ai-code-mcp/git-pull.md

WHAT IT DOES

What git_pull does on Code MCP Server

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

RISK

Why git_pull is rated Medium

git_pull modifies the workspace by applying remote changes to local files, branches, and repository state. While not permanently destructive, it is a Write operation that can overwrite local modifications and alter the codebase. Severity is high because uncontrolled pulls could overwrite developer work, introduce malicious code into the workspace, or break the project state.

From the tool's definition Tool name 'git_pull' and description 'Pull changes from remote' indicates fetching and applying remote changes to local repository, which modifies local files and state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs git_pull safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Code MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For git_pull, this is the rule to start with:

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.

The button opens the PolicyLayer dashboard: create your workspace, connect Code MCP Server, apply this rule, and every git_pull call is checked against it from then on.

FAQ

Questions about git_pull

What does the git_pull tool do? +

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

Register the Code MCP 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 Code MCP 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 Code MCP Server MCP server (agentics-ai/code-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Code MCP Server, and thousands of servers like it.

This server

All 73 Code MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →