Arquivar canais inativos automaticamente
AI agents call archive_old_channels to permanently remove resources in Slack MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Archiving Slack channels is effectively irreversible in practice (requires manual unarchiving by an admin) and affects all members of those channels, removing their ability to post or interact. The tool operates automatically ('automaticamente') on multiple channels, amplifying the blast radius. This qualifies as Destructive due to the irreversible nature of bulk channel archiving.
From the tool's definition 'archive_old_channels' - archiving channels is an irreversible or difficult-to-reverse operation that removes active access to channel history and membership for all users
Attacks that exploit this kind of access
Arquivar canais inativos automaticamente. It is categorised as a Destructive tool in the Slack MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Slack MCP Server MCP server in PolicyLayer and add a rule for archive_old_channels: 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 MCP Server. Nothing to install.
archive_old_channels 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 archive_old_channels 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 archive_old_channels. 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.
archive_old_channels is provided by the Slack MCP Server MCP server (will2023a/mcp-slack). 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 →