Remove untracked files from the working directory. Deletes files that aren
AI agents call git_clean to permanently remove resources in Git MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The git_clean command irreversibly deletes untracked files from the working directory with no undo mechanism. This is a destructive operation that cannot be reversed, making it more severe than Write operations. While the blast radius is somewhat limited to untracked files in a single repository, the permanent data loss justifies 'high' severity.
From the tool's definition Tool name 'git_clean' and description 'Remove untracked files from the working directory. Deletes files that aren' (truncated) explicitly indicate permanent deletion of files.
Attacks that exploit this kind of access
Remove untracked files from the working directory. Deletes files that aren. It is categorised as a Destructive tool in the Git MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Git 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 Git 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 Git MCP Server MCP server (wty0512/git-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →