AI agents use chat_schedule_message to create or update resources in Slack — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Slack environment.
Scheduling a message is a write operation that creates new data in Slack (a scheduled message object) and will cause side effects (message delivery) at a future time. While the description is empty, the name and context of sibling write/create tools justify Write classification.
From the tool's definition Tool name 'chat_schedule_message' indicates scheduling/creating messages in Slack. Sibling tools include 'apps_manifest_create', 'apps_manifest_update', and similar write/create operations, suggesting this server's tools perform state-modifying actions.
Attacks that exploit this kind of access
chat_schedule_message. It is categorised as a Write tool in the Slack MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Slack MCP server in PolicyLayer and add a rule for chat_schedule_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_schedule_message is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the chat_schedule_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_schedule_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_schedule_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 →