chat_delete_scheduled_message
AI agents call chat_delete_scheduled_message 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.
Deletion is irreversible and destroys data. Even though the description is empty, the tool name unambiguously indicates it removes a scheduled message from Slack. This is irreversible data loss, placing it in the Destructive category. Severity is high because an agent could delete many scheduled messages if given loop/automation capability.
From the tool's definition Tool name 'chat_delete_scheduled_message' explicitly performs deletion of a scheduled message; 'delete' is a destructive operation that cannot be undone.
Attacks that exploit this kind of access
chat_delete_scheduled_message. 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_scheduled_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 Slack. Nothing to install.
chat_delete_scheduled_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 chat_delete_scheduled_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 chat_delete_scheduled_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.
chat_delete_scheduled_message 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.
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 →