Delete a channel (legacy undocumented).
AI agents call channels_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.
Deleting a channel is an irreversible destructive action that cannot be undone. It removes all messages, files, and metadata within that channel, affecting all users who depend on it. This is the most severe category applicable. Severity is 'high' rather than 'critical' because the blast radius is limited to a single workspace channel, though the impact on team collaboration can be significant.
From the tool's definition Tool name is 'channels_delete' and description states 'Delete a channel'; this irreversibly removes a Slack channel and all its associated data.
Attacks that exploit this kind of access
Delete a channel (legacy undocumented). 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 channels_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.
channels_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 channels_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 channels_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.
channels_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 →