Delete a file from repository.
AI agents call delete_file to permanently remove resources in GitLab MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes data (a file) from a repository. While git technically preserves history, the primary effect is destructive—the file is removed from the working state. The blast radius is high: an agent could delete critical source code, configuration files, or documentation. Confidence is high because the name and description are unambiguous.
From the tool's definition Tool name is 'delete_file' with description 'Delete a file from repository.' The verb 'delete' is explicitly destructive, and files deleted from a repository cannot be recovered without access to git history or backups.
Attacks that exploit this kind of access
Delete a file from repository. It is categorised as a Destructive tool in the GitLab MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the GitLab MCP Server MCP server in PolicyLayer and add a rule for delete_file: 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 GitLab MCP Server. Nothing to install.
delete_file 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 delete_file 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 delete_file. 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.
delete_file is provided by the GitLab MCP Server MCP server (skmprb/gitlab-clone-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 →