This record as markdown: /tools/karbassi-slack-mcp/slack-lists-items-delete-multiple.md
What slack_lists_items_delete_multiple does on Slack
AI agents call slack_lists_items_delete_multiple 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.
Why slack_lists_items_delete_multiple is rated Critical
Deletion operations that remove data permanently fall under the Destructive category, which takes precedence over Write. The ability to delete multiple items at once increases the blast radius.
From the tool's definition Tool name contains 'delete' and description states 'Delete multiple list items' - this is an irreversible deletion operation that destroys data without undo capability.
Attacks that exploit this kind of access
The rule that runs slack_lists_items_delete_multiple safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Slack, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For slack_lists_items_delete_multiple, this is the rule to start with:
slack_lists_items_delete_multiple is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Slack, apply this rule, and every slack_lists_items_delete_multiple call is checked against it from then on.
Questions about slack_lists_items_delete_multiple
Delete multiple list items. 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 slack_lists_items_delete_multiple: 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.
slack_lists_items_delete_multiple 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 slack_lists_items_delete_multiple 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 slack_lists_items_delete_multiple. 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.
slack_lists_items_delete_multiple 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.
More on Slack, and thousands of servers like it.
Across the catalogue