delete_application
AI agents call delete_application 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 an application in an Okta organization cannot be undone and has significant blast radius—it affects all users with access to that application and may disrupt authentication flows or integrations. This meets the Destructive category definition (irreversibly deletes data).
From the tool's definition Tool name is 'delete_application' with no description provided. The 'delete_' prefix combined with the sibling tool 'confirm_delete_application' indicates this irreversibly removes an application from an Okta organization.
Attacks that exploit this kind of access
delete_application. 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_application: 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_application 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_application 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_application. 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_application 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 →