Permanently deletes an app created through app manifests.
AI agents call apps_manifest_delete to permanently remove resources in Slack — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes an entire app, which cannot be undone. The permanent deletion of app manifests and associated configurations represents a destructive action with significant blast radius in a Slack workspace context. Even if not directly affecting user data, deleting apps can disrupt workflows and integrations.
From the tool's definition Tool description states "Permanently deletes an app created through app manifests" — the use of "Permanently deletes" directly indicates irreversible deletion of data/configuration.
Attacks that exploit this kind of access
Permanently deletes an app created through app manifests. It is categorised as a Destructive tool in the Slack MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Slack MCP server in PolicyLayer and add a rule for apps_manifest_delete: 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 Slack. Nothing to install.
apps_manifest_delete 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 apps_manifest_delete 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 apps_manifest_delete. 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.
apps_manifest_delete is provided by the Slack MCP server (karbassi/slack-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 →