This record as markdown: /tools/karbassi-slack-mcp/chat-delete.md
What chat_delete does on Slack
AI agents call chat_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 chat_delete is rated Critical
Deletion of chat messages is an irreversible action that cannot be undone. This falls into the Destructive category per the classification rules. The severity is high due to potential loss of important communication records and organizational data. Confidence is high based on the clear delete operation implied by the name, despite the empty description.
From the tool's definition Tool name 'chat_delete' indicates deletion of chat messages. The tool description is empty, but the name and context within a Slack MCP server that provides access to messages clearly suggest irreversible removal of message data.
Attacks that exploit this kind of access
The rule that runs chat_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 chat_delete, this is the rule to start with:
chat_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 chat_delete call is checked against it from then on.
Questions about chat_delete
chat_delete is a destructive tool on the Slack MCP server. 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 chat_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.
chat_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 chat_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 chat_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.
chat_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