admin_rename_user

Rename a user (requires admin privileges)

SERVERForgejo SOURCEsqcows/forgejo-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sqcows-forgejo-mcp/admin-rename-user.md

WHAT IT DOES

What admin_rename_user does on Forgejo

AI agents use admin_rename_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.

RISK

Why admin_rename_user is rated Medium

Modifies user identity reversibly but affects access control and system state significantly.

From the tool's definition Rename a user; requires admin privileges.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs admin_rename_user safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Forgejo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For admin_rename_user, this is the rule to start with:

admin_rename_user Rate-limited

admin_rename_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "admin_rename_user": {
      "limits": [
        {
          "counter": "admin_rename_user_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Forgejo, apply this rule, and every admin_rename_user call is checked against it from then on.

FAQ

Questions about admin_rename_user

What does the admin_rename_user tool do? +

Rename a 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.

How do I enforce a policy on admin_rename_user? +

Register the Forgejo MCP server in PolicyLayer and add a rule for admin_rename_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.

What risk level is admin_rename_user? +

admin_rename_user is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit admin_rename_user? +

Yes. Add a rate_limit block to the admin_rename_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.

How do I block admin_rename_user completely? +

Set action: deny in the PolicyLayer policy for admin_rename_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.

What MCP server provides admin_rename_user? +

admin_rename_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.

KEEP EXPLORING

More on Forgejo, and thousands of servers like it.

This server

All 457 Forgejo tools →

Across the catalogue

rotate_keys_admin on 0sec → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →