git_remove_all
Removes all files from the staging area
This record as markdown: /tools/0xshariq-github-mcp-server/git-remove-all.md
What git_remove_all does on GitHub MCP Server
AI agents call git_remove_all to permanently remove resources in GitHub MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why git_remove_all is rated Critical
Unstaging all files is a bulk operation that reverses staged changes across the entire repository. While it doesn't permanently delete files from disk, removing all files from the staging area in bulk is difficult to recover from in automated workflows and can cause significant loss of carefully staged work. The 'all' scope makes this a high-severity action with destructive characteristics.
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
The rule that runs git_remove_all safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GitHub MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For git_remove_all, this is the rule to start with:
git_remove_all is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect GitHub MCP Server, apply this rule, and every git_remove_all call is checked against it from then on.
Questions about git_remove_all
Removes all files from the staging area. It is categorised as a Destructive tool in the GitHub MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
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.
git_remove_all is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
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.
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.
git_remove_all is provided by the GitHub MCP Server MCP server (0xshariq/github-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GitHub MCP Server, and thousands of servers like it.
Across the catalogue