subscriptions_thread_mark
A write tool on the Slack MCP server.
This record as markdown: /tools/karbassi-slack-mcp/subscriptions-thread-mark.md
What subscriptions_thread_mark does on Slack
AI agents use subscriptions_thread_mark 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 subscriptions_thread_mark is rated Medium
Without a description, classification relies on naming convention and server context. The 'subscriptions_thread_mark' name suggests modifying subscription state (likely enabling/disabling notifications or marking a thread as subscribed), which is a reversible write operation.
From the tool's definition Tool name 'subscriptions_thread_mark' indicates a mark/subscription action on threads. Given the sibling tools operate on Slack channels, threads, and messages, and the 'mark' pattern typically implies setting a subscription state or flag on a thread object.
Attacks that exploit this kind of access
The rule that runs subscriptions_thread_mark 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 subscriptions_thread_mark, this is the rule to start with:
subscriptions_thread_mark 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 subscriptions_thread_mark call is checked against it from then on.
Questions about subscriptions_thread_mark
subscriptions_thread_mark 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 subscriptions_thread_mark: 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.
subscriptions_thread_mark 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 subscriptions_thread_mark 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 subscriptions_thread_mark. 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.
subscriptions_thread_mark 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