git_restore · Git MCP: Risk & Policy

WHAT IT DOES

What git_restore does on Git

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

WHY IT NEEDS A POLICY

Why git_restore needs a policy

git_restore modifies files and the index by restoring them to a previous state. While this is reversible (you can restore again to a different state), it does overwrite local changes. It is not destructive in the sense of permanent deletion (that would be git_clean with -f). It's more severe than a Read operation because it alters the local state, but less severe than Destructive operations like deletion.

From the tool's definition Tool description states it can 'Restore paths in worktree and/or index from current state or source ref', which modifies the working tree and staging area. This is a write operation that changes file contents and index state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git_restore Rate-limited

git_restore 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_restore": {
      "limits": [
        {
          "counter": "git_restore_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, so you can run agents against it safely.

FAQ

Questions about git_restore

What does the git_restore tool do? +

Restore paths in worktree and/or index from current state or source ref. It is categorised as a Write tool in the Git 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_restore? +

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

What risk level is git_restore? +

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

Can I rate-limit git_restore? +

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

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

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