Edit an existing user (requires admin privileges)
AI agents use admin_edit_user to create or update resources in Forgejo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Forgejo environment.
This tool modifies user records (name, email, password, permissions, etc.) which are critical administrative data. While reversible (changes can be undone via subsequent edits), the high-privilege requirement and potential to alter security-sensitive user attributes (passwords, roles, activation status) makes misuse high-severity.
From the tool's definition Tool name 'admin_edit_user' and description 'Edit an existing user (requires admin privileges)' indicate modification of user data.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access admin_edit_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_edit_user:
{
"version": "1",
"default": "deny",
"tools": {
"admin_edit_user": {
"limits": [
{
"counter": "admin_edit_user_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}admin_edit_user stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Edit an existing user (requires admin privileges). It is categorised as a Write tool in the Forgejo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Forgejo MCP server in PolicyLayer and add a rule for admin_edit_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_edit_user is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the admin_edit_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_edit_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_edit_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.