Delete a user. Content owned by the user is reassigned to replaceId.
AI agents call wiki_user_delete to permanently remove resources in Mcp Wikijs Mv — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
User deletion is a destructive operation that permanently removes a user account from the system. While content is reassigned rather than lost, the user account itself is irreversibly deleted and cannot be recovered. This falls under the Destructive category as it involves irreversible removal of data/entities.
From the tool's definition Delete a user. Content owned by the user is reassigned to replaceId. The tool name contains 'delete' and the description explicitly states user deletion, which is an irreversible action that cannot be undone.
Attacks that exploit this kind of access
Delete a user. Content owned by the user is reassigned to replaceId. It is categorised as a Destructive tool in the Mcp Wikijs Mv MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Wikijs Mv MCP server in PolicyLayer and add a rule for wiki_user_delete: 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 Mcp Wikijs Mv. Nothing to install.
wiki_user_delete 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 wiki_user_delete 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 wiki_user_delete. 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.
wiki_user_delete is provided by the Mcp Wikijs Mv MCP server (janschachtschabel/mcp-for-wiki-js). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →