Repository cleanup and maintenance with backup options
AI agents call git_clean 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.
git_clean maps directly to `git clean`, which permanently deletes untracked files and directories from the repository. While the description mentions 'backup options' (slightly lowering confidence), the core operation is irreversible deletion of untracked content. Misuse by an AI agent could result in permanent loss of uncommitted work, making this Destructive with high severity.
From the tool's definition 'Repository cleanup' and 'maintenance' — git clean removes untracked files/directories from the working tree, which is irreversible without backup
Attacks that exploit this kind of access
Repository cleanup and maintenance with backup options. 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_clean: 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_clean 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_clean 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_clean. 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_clean 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.
git_clean is one line of GitHub MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →