delete_user

Delete a Redmine user (requires admin). confirm must be true.

Server Redmine MCP OAuth Server zh/redmine_mcp_py
Category Destructive
Risk class Critical
Parameters 00 required

What delete_user does on Redmine MCP OAuth Server

AI agents call delete_user to permanently remove resources in Redmine MCP OAuth Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_user needs a policy

Deleting a user is an irreversible operation that removes data from the system and cannot be undone. This qualifies as Destructive rather than Write (which is reversible). The critical severity reflects that unauthorized or erroneous deletion of user accounts in a project management system like Redmine could disable team members' access, lose historical data associations, and disrupt project operations at scale.

From the tool's definition Tool name 'delete_user' combined with description 'Delete a Redmine user' explicitly indicates irreversible deletion of user records. The requirement for admin permissions and 'confirm must be true' reflects the destructive nature of this action.

Risk signalsAdmin/system-level operation

Questions about delete_user

What does the delete_user tool do? +

Delete a Redmine user (requires admin). confirm must be true. It is categorised as a Destructive tool in the Redmine MCP OAuth Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_user? +

Register the Redmine MCP OAuth Server MCP server in PolicyLayer and add a rule for 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 Redmine MCP OAuth Server. Nothing to install.

What risk level is delete_user? +

delete_user is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_user? +

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

How do I block delete_user completely? +

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

What MCP server provides delete_user? +

delete_user is provided by the Redmine MCP OAuth Server MCP server (zh/redmine_mcp_py). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

delete_user is one line of Redmine MCP OAuth Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.