auth user(계정) 삭제.
AI agents call delete_auth_user_tool to permanently remove resources in F5 MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting authentication users is an irreversible destructive action that cannot be recovered. This ranks above Execute because the consequence is permanent data loss of security credentials. Even if misused by an AI agent, the damage—loss of user accounts and access rights—cannot be easily restored without administrative intervention and audit logs.
From the tool's definition Tool name contains 'delete' and description states 'auth user(계정) 삭제' (delete auth user/account). This irreversibly removes authentication credentials and cannot be undone.
Attacks that exploit this kind of access
auth user(계정) 삭제. It is categorised as a Destructive tool in the F5 MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the F5 MCP Server MCP server in PolicyLayer and add a rule for delete_auth_user_tool: 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 F5 MCP Server. Nothing to install.
delete_auth_user_tool 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_auth_user_tool 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_auth_user_tool. 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_auth_user_tool is provided by the F5 MCP Server MCP server (mink0119/f5-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 →