This record as markdown: /tools/karbassi-slack-mcp/slack-lists-items-delete.md
What slack_lists_items_delete does on Slack
AI agents call slack_lists_items_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.
Why slack_lists_items_delete is rated Critical
Deletion is inherently destructive and cannot be undone. While the blast radius is limited to a single list item (not company-wide), the irreversible nature of deletion and potential for accidental or malicious removal of important shared data in a collaborative workspace justifies 'high' severity. Confidence is very high due to unambiguous language.
From the tool's definition Tool name explicitly states 'delete' and description confirms 'Delete a list item' — this irreversibly removes data from Slack lists.
Attacks that exploit this kind of access
The rule that runs slack_lists_items_delete 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, this is the rule to start with:
slack_lists_items_delete 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 call is checked against it from then on.
Questions about slack_lists_items_delete
Delete a list item. 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: 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 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 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. 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 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