git_reset · GitHub MCP Server MCP: Risk & Policy

WHAT IT DOES

What git_reset does on GitHub MCP Server

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

WHY IT NEEDS A POLICY

Why git_reset needs a policy

git_reset here unstages staged changes (i.e., moves files from the index back to the working tree). This is a reversible operation — it does not delete files or commits — making it a Write-level action. However, misuse could disrupt a carefully prepared commit, hence medium severity.

From the tool's definition 'Unstages all staged changes' — reverses the staging of changes, modifying the git index state

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches GitHub MCP Server, so you can run agents against it safely.

FAQ

Questions about git_reset

What does the git_reset tool do? +

Unstages all staged changes. It is categorised as a Write tool in the GitHub 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_reset? +

Register the GitHub MCP Server 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 GitHub MCP Server. 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 GitHub MCP Server MCP server (lyderdev/github-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.