AI agents invoke chat_start_stream to trigger actions in Slack. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool performs an action that triggers Slack's message streaming mechanism—an operation whose effects depend on arguments and cannot be undone without further action. This is Execute rather than Write because it initiates an active communication stream (a triggered operation) rather than simply creating/modifying a static piece of data.
From the tool's definition Tool name is 'chat_start_stream' on a Slack MCP server that provides full access to Slack messaging and communication features.
Attacks that exploit this kind of access
chat_start_stream. It is categorised as a Execute tool in the Slack MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Slack MCP server in PolicyLayer and add a rule for chat_start_stream: 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_start_stream is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the chat_start_stream 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_start_stream. 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_start_stream 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 →