Deactivate an Okta user. This transitions the user to DEPROVISIONED status.
AI agents call okta_deactivate_user to permanently remove resources in Integrations MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deactivating and deprovisioning a user in Okta is a highly impactful, difficult-to-reverse action that removes the user's access across all integrated applications. While technically not a 'delete,' transitioning to DEPROVISIONED status is functionally irreversible in practice and cuts off all access, making it Destructive with critical severity due to the blast radius of locking out a legitimate user from all…
From the tool's definition Deactivate an Okta user. This transitions the user to DEPROVISIONED status.
Attacks that exploit this kind of access
Deactivate an Okta user. This transitions the user to DEPROVISIONED status. It is categorised as a Destructive tool in the Integrations MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Integrations MCP server in PolicyLayer and add a rule for okta_deactivate_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 Integrations MCP. Nothing to install.
okta_deactivate_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 okta_deactivate_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 okta_deactivate_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.
okta_deactivate_user is provided by the Integrations MCP server (shriram-vasudevan/integrations-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 →