git_init · Git MCP Server MCP: Risk & Policy

WHAT IT DOES

What git_init does on Git MCP Server

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

WHY IT NEEDS A POLICY

Why git_init needs a policy

git_init creates new repository metadata and directory structures, which is a reversible write operation. While the changes can be undone by deleting the created .git directory, the tool modifies the filesystem state. It does not execute arbitrary code, delete existing repositories, or move money.

From the tool's definition "Initialize a new Git repository. Creates the necessary directory structure and Git metadata for a new Git repository at the specified path." This operation creates new files and directories (.git directory and metadata) that represent a persistent change to…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git_init Rate-limited

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

FAQ

Questions about git_init

What does the git_init tool do? +

Initialize a new Git repository. Creates the necessary directory structure and Git metadata for a new Git repository at the specified path. The repository can be created as a standard repository with a working directory or as a bare repository (typically used for centralized repositories). Creates a. It is categorised as a Write tool in the Git 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_init? +

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

What risk level is git_init? +

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

Can I rate-limit git_init? +

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

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

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