Delete a previously sent Slack message using its conversation ID and timestamp.
AI agents call slack_delete_message to permanently remove resources in Slackxmcp — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting messages cannot be undone and permanently removes communication data from Slack. While the blast radius is limited to a single message rather than bulk data, it is destructive in nature and warrants the Destructive category.
From the tool's definition Tool name is 'slack_delete_message' and description states 'Delete a previously sent Slack message' - the verb 'delete' combined with the action of removing a message indicates irreversible data destruction.
Attacks that exploit this kind of access
Delete a previously sent Slack message using its conversation ID and timestamp. It is categorised as a Destructive tool in the Slackxmcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Slackx MCP server in PolicyLayer and add a rule for slack_delete_message: 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 Slackxmcp. Nothing to install.
slack_delete_message 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_delete_message 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_delete_message. 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_delete_message is provided by the Slackx MCP server (vaibhavpandeyvpz/slackxmcp). 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 →