okta_deactivate_user

Deactivate an Okta user. This transitions the user to DEPROVISIONED status.

SERVERIntegrations MCP SOURCEshriram-vasudevan/integrations-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/shriram-vasudevan-integrations-mcp/okta-deactivate-user.md

WHAT IT DOES

What okta_deactivate_user does on Integrations MCP

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.

RISK

Why okta_deactivate_user is rated Critical

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

RECOMMENDED RULE

The rule that runs okta_deactivate_user safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Integrations MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For okta_deactivate_user, this is the rule to start with:

okta_deactivate_user Hidden

okta_deactivate_user is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "okta_deactivate_user"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Integrations MCP, apply this rule, and every okta_deactivate_user call is checked against it from then on.

FAQ

Questions about okta_deactivate_user

What does the okta_deactivate_user tool do? +

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.

How do I enforce a policy on okta_deactivate_user? +

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.

What risk level is okta_deactivate_user? +

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.

Can I rate-limit okta_deactivate_user? +

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.

How do I block okta_deactivate_user completely? +

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.

What MCP server provides okta_deactivate_user? +

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.

KEEP EXPLORING

More on Integrations, and thousands of servers like it.

This server

All 420 Integrations tools → Critical-risk tools on this server →

Across the catalogue

delete_mysql_user on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →