delete_deactivated_user
AI agents call delete_deactivated_user to permanently remove resources in Okta MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes user data from an Okta organization, which is irreversible and cannot be undone. Deletion of user identity records is a destructive operation with severe consequences—loss of audit trails, access revocation, and potential data loss. Even though the user is 'deactivated' first, the delete operation itself is destructive.
From the tool's definition Tool name 'delete_deactivated_user' indicates permanent deletion of user records. The verb 'delete' combined with the Okta context (identity management system where user records are critical data) indicates an irreversible action.
Attacks that exploit this kind of access
delete_deactivated_user. It is categorised as a Destructive tool in the Okta MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Okta MCP Server MCP server in PolicyLayer and add a rule for delete_deactivated_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 Okta MCP Server. Nothing to install.
delete_deactivated_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_deactivated_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_deactivated_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_deactivated_user is provided by the Okta MCP Server MCP server (pranav-okta/okta-mcp-server). 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 →