Delete a user from Okta (must be deactivated first)
AI agents call delete_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 and irreversibly deletes user accounts from Okta's identity management system. This is a destructive action with high blast radius—a misdirected or malicious deletion could remove critical user accounts, disrupt authentication infrastructure, and create operational chaos.
From the tool's definition Tool name 'delete_user' combined with description 'Delete a user from Okta' indicates irreversible removal of user identity data from the system. Deletion of user accounts cannot be undone and removes all associated authentication and access control records.
Documented attack patterns abuse exactly the kind of access delete_user gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Okta MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_user:
{
"version": "1",
"default": "deny",
"hide": [
"delete_user"
]
}delete_user disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a user from Okta (must be deactivated first). 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_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_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 Okta MCP Server MCP server (kapilduraphe/okta-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Okta MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 Okta MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.