assistant_threads_set_status
A write tool on the Slack MCP server.
This record as markdown: /tools/karbassi-slack-mcp/assistant-threads-set-status.md
What assistant_threads_set_status does on Slack
AI agents use assistant_threads_set_status 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.
Why assistant_threads_set_status is rated Medium
This tool appears to modify thread status (a reversible change to metadata/state) rather than create/delete threads or execute code. The 'set' operation is consistent with Write category tools that update existing resources. Without an explicit description, confidence is moderate.
From the tool's definition Tool name 'assistant_threads_set_status' indicates modification of thread status state. The verb 'set' combined with 'status' suggests a state-changing operation.
Attacks that exploit this kind of access
The rule that runs assistant_threads_set_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Slack, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For assistant_threads_set_status, this is the rule to start with:
assistant_threads_set_status stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Slack, apply this rule, and every assistant_threads_set_status call is checked against it from then on.
Questions about assistant_threads_set_status
assistant_threads_set_status is a write tool on the Slack MCP server. 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 assistant_threads_set_status: 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.
assistant_threads_set_status 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 assistant_threads_set_status 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 assistant_threads_set_status. 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.
assistant_threads_set_status 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.
More on Slack, and thousands of servers like it.
This server
Across the catalogue