AI agents call delete_file to permanently remove resources in Forgejo — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a file from a repository is an irreversible action that cannot be undone without access to version history recovery mechanisms. This fits the Destructive category as it permanently removes data from the repository. Severity is high because an AI agent misusing this tool could delete critical source code, configuration files, or documentation, causing significant operational impact.
From the tool's definition Tool name: 'delete_file'; description: 'Delete a file from a repository'. The verb 'delete' indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access delete_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Forgejo, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_file:
{
"version": "1",
"default": "deny",
"hide": [
"delete_file"
]
}delete_file disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a file from a repository. It is categorised as a Destructive tool in the Forgejo MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Forgejo 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 Forgejo. 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 Forgejo MCP server (sqcows/forgejo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Forgejo, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
103 Forgejo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.