AI agents call admin_delete_user 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 user account is an irreversible destructive action that permanently removes user data and access. This is the most severe category applicable. The blast radius is critical because an AI agent with this capability could maliciously or accidentally eliminate user accounts, removing their repositories, issues, and authentication records.
From the tool's definition Tool name is 'admin_delete_user' and description states 'Delete a user (requires admin privileges)'. The verb 'delete' and the absence of any mention of soft-delete, recovery, or reversal indicates irreversible removal of a user account.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access admin_delete_user 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 admin_delete_user:
{
"version": "1",
"default": "deny",
"hide": [
"admin_delete_user"
]
}admin_delete_user 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 user (requires admin privileges). 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 admin_delete_user: 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.
admin_delete_user 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 admin_delete_user 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 admin_delete_user. 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.
admin_delete_user 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.