AI agents call chat_scheduled_messages_list to retrieve information from Slack without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the naming convention, this tool retrieves or queries scheduled messages from Slack without creating, modifying, or deleting data. The '_list' suffix is a standard pattern for read-only operations in Slack's API. No side effects are indicated. Even with an empty description, the name structure provides sufficient evidence for Read classification.
From the tool's definition Tool name 'chat_scheduled_messages_list' indicates a list/query operation. The '_list' suffix strongly suggests retrieval without modification. Description is empty, reducing confidence slightly.
Attacks that exploit this kind of access
chat_scheduled_messages_list. It is categorised as a Read tool in the Slack MCP Server, which means it retrieves data without modifying state.
Register the Slack MCP server in PolicyLayer and add a rule for chat_scheduled_messages_list: 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_scheduled_messages_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the chat_scheduled_messages_list 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_scheduled_messages_list. 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_scheduled_messages_list 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 →