git_operation

Execute a git operation in the project repository.

SERVERCode SOURCE54yyyu/code-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/54yyyu-code-mcp/git-operation.md

WHAT IT DOES

What git_operation does on Code

AI agents invoke git_operation to trigger actions in Code. 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.

RISK

Why git_operation is rated High

While git operations can range from read-only (log, status) to destructive (force-push, reset --hard), the tool permits execution of git commands whose effects depend entirely on arguments provided by the AI agent. This is classic Execute category behavior—triggering external operations with argument-dependent consequences.

From the tool's definition Tool is described as 'Execute a git operation in the project repository' and exists alongside tools that 'run terminal commands' and 'manage git'. Git operations can include arbitrary commands with side effects (rebasing, force-pushing, resetting, bisecting).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs git_operation safely

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

git_operation Rate-limited

git_operation 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_operation": {
      "limits": [
        {
          "counter": "git_operation_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about git_operation

What does the git_operation tool do? +

Execute a git operation in the project repository. It is categorised as a Execute tool in the Code 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_operation? +

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

What risk level is git_operation? +

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

Can I rate-limit git_operation? +

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

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

git_operation is provided by the Code MCP server (54yyyu/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, and thousands of servers like it.

This server

All 9 Code tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →