AI agents use assistant_threads_set_title 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.
This tool modifies thread metadata (title) in a reversible manner. While the change could affect how conversations are organized or understood by workspace members, the modification is non-destructive and can be easily changed back. Classified as Write rather than Execute because it directly modifies a specific field rather than running arbitrary code.
From the tool's definition Tool performs 'Set the title' action on an existing resource (AI assistant thread), which is a reversible modification operation. The description explicitly indicates modification of thread metadata without deletion or financial impact.
Attacks that exploit this kind of access
Set the title for an AI assistant thread. 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_title: 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_title 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_title 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_title. 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_title 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 →