confirm_delete_group
AI agents call confirm_delete_group 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.
Deleting a group in Okta is irreversible and can affect multiple users' access, permissions, and organizational structure. This is a Destructive action (higher severity than Write/Execute) with critical blast radius if triggered inappropriately by an AI agent. The 'confirm_delete' pattern suggests this is a secondary confirmation step following group deletion initiation.
From the tool's definition Tool name contains 'delete' and 'confirm_delete' prefix, indicating irreversible deletion of a group resource. Empty description limits detail, but the naming pattern and context (Okta group management) clearly indicates permanent removal.
Attacks that exploit this kind of access
confirm_delete_group. 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 confirm_delete_group: 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.
confirm_delete_group 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 confirm_delete_group 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 confirm_delete_group. 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.
confirm_delete_group 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 →