git_reset

Unstage all staged changes

SERVERGit SOURCE@modelcontextprotocol/server-git

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity verified Pull the record →

This record as markdown: /tools/git/git-reset.md

WHAT IT DOES

What git_reset does on Git

AI agents use git_reset 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.

RISK

Why git_reset is rated Medium

git_reset here unstages changes (moves them from the index back to the working tree), which is a reversible modification to the repository's staging area. No data is permanently deleted — the changes still exist in the working directory.

From the tool's definition Tool name 'git_reset' and description 'Unstage all staged changes'

Risk signalsDiscards staging area state

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs git_reset safely

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

git_reset Rate-limited

git_reset 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_reset": {
      "limits": [
        {
          "counter": "git_reset_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 Git, apply this rule, and every git_reset call is checked against it from then on.

FAQ

Questions about git_reset

What does the git_reset tool do? +

Unstage all staged changes. 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_reset? +

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

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

Can I rate-limit git_reset? +

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

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

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

KEEP EXPLORING

More on Git, and thousands of servers like it.

This server

All 14 Git tools →

Across the catalogue

The MCP Attack Database →

Guides

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