Delete a user. Requires confirm=True.
AI agents call delete_user to permanently remove resources in Truenas Ws — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a user account is a destructive operation that cannot be undone and removes access credentials and associated permissions. While the confirmation requirement provides a safeguard, the tool itself performs an irreversible action affecting system authentication and authorization. This is more severe than Write (which is reversible) and warrants the Destructive category.
From the tool's definition Tool name is 'delete_user' and description states 'Delete a user' — this is an irreversible deletion operation. The requirement for 'confirm=True' does not change the fundamental destructive nature of the action.
Attacks that exploit this kind of access
Delete a user. Requires confirm=True. It is categorised as a Destructive tool in the Truenas Ws MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Truenas Ws 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 Truenas Ws. Nothing to install.
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 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 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.
delete_user is provided by the Truenas Ws MCP server (thoriphes/truenas-ws-mcp). 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 →