Permanently delete a hosted app and all its data.
AI agents call vibekit_delete_app to permanently remove resources in Vibekit — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes hosted applications and associated data with no undo capability. The blast radius is critical because an AI agent misusing this tool could destroy entire production deployments and lose all persisted application state and user data. This is the most severe category applicable.
From the tool's definition Tool name contains 'delete_app' and description explicitly states 'Permanently delete a hosted app and all its data.' The use of 'Permanently' and 'all its data' confirms irreversible deletion with complete data loss.
Attacks that exploit this kind of access
Permanently delete a hosted app and all its data. It is categorised as a Destructive tool in the Vibekit MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Vibekit MCP server in PolicyLayer and add a rule for vibekit_delete_app: 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 Vibekit. Nothing to install.
vibekit_delete_app 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 vibekit_delete_app 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 vibekit_delete_app. 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.
vibekit_delete_app is provided by the Vibekit MCP server (vibekit-apps/vibekit-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 →