git-remove-all · GitHub MCP Server MCP: Risk & Policy

WHAT IT DOES

What git-remove-all does on GitHub MCP Server

AI agents use git-remove-all 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-remove-all needs a policy

This tool unstages all files (equivalent to 'git reset HEAD' or 'git restore --staged'), which modifies the Git index/staging area. This is a reversible write operation — it does not delete files from disk or history, just removes them from the staging area. However, misuse could cause loss of staged changes context, warranting medium severity.

From the tool's definition Removes all files from the staging area

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git-remove-all Rate-limited

git-remove-all 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-remove-all": {
      "limits": [
        {
          "counter": "git-remove-all_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-remove-all

What does the git-remove-all tool do? +

Removes all files from the staging area. 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-remove-all? +

Register the GitHub MCP Server MCP server in PolicyLayer and add a rule for git-remove-all: 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-remove-all? +

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

Can I rate-limit git-remove-all? +

Yes. Add a rate_limit block to the git-remove-all 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-remove-all completely? +

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

git-remove-all is provided by the GitHub MCP Server MCP server (jungchihoon/github-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.