assistant_threads_set_status · Slack MCP: Risk & Policy

WHAT IT DOES

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 IT NEEDS A POLICY

Why assistant_threads_set_status needs a policy

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

Recommended rule Ready

Verdict

assistant_threads_set_status Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "assistant_threads_set_status": {
      "limits": [
        {
          "counter": "assistant_threads_set_status_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Slack, so you can run agents against it safely.

FAQ

Questions about assistant_threads_set_status

What does the assistant_threads_set_status tool do? +

assistant_threads_set_status. 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.

How do I enforce a policy on assistant_threads_set_status? +

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.

What risk level is assistant_threads_set_status? +

assistant_threads_set_status is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit assistant_threads_set_status? +

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.

How do I block assistant_threads_set_status completely? +

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.

What MCP server provides assistant_threads_set_status? +

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.