git_set_working_dir · Git MCP Server MCP: Risk & Policy

WHAT IT DOES

What git_set_working_dir does on Git MCP Server

AI agents use git_set_working_dir 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_set_working_dir needs a policy

This tool modifies application state (the working directory context) that persists across future operations. While not directly creating or deleting repository content, it is a reversible configuration change that Write appropriately captures.

From the tool's definition "Set a global working directory path for all Git operations" — this modifies the operational state/configuration that affects subsequent tool behavior. The tool changes where Git operations are rooted, which is a state modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git_set_working_dir Rate-limited

git_set_working_dir 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_set_working_dir": {
      "limits": [
        {
          "counter": "git_set_working_dir_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_set_working_dir

What does the git_set_working_dir tool do? +

Set a global working directory path for all Git operations. Future tool calls can use. 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_set_working_dir? +

Register the Git MCP Server MCP server in PolicyLayer and add a rule for git_set_working_dir: 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_set_working_dir? +

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

Can I rate-limit git_set_working_dir? +

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

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

git_set_working_dir 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.