Get all replies in a message thread
AI agents call slack_get_thread_replies to retrieve information from Simple Slack without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves thread replies from Slack without creating, modifying, or deleting data. It is a query operation that fetches existing information. The blast radius of misuse is minimal—an agent could read private conversations it shouldn't access, but cannot cause financial loss, execute code, or destroy data. Low severity is appropriate for informational disclosure risks in this context.
From the tool's definition Tool name 'slack_get_thread_replies' and description 'Get all replies in a message thread' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get all replies in a message thread. It is categorised as a Read tool in the Simple Slack MCP Server, which means it retrieves data without modifying state.
Register the Simple Slack MCP server in PolicyLayer and add a rule for slack_get_thread_replies: 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 Simple Slack. Nothing to install.
slack_get_thread_replies 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 slack_get_thread_replies 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_get_thread_replies. 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_get_thread_replies is provided by the Simple Slack MCP server (bugzy-ai/slack-mcp-server). 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 →