subscriptions_thread_mark · Slack MCP: Risk & Policy

WHAT IT DOES

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

Why subscriptions_thread_mark needs a policy

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

Recommended rule Ready

Verdict

subscriptions_thread_mark Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "subscriptions_thread_mark": {
      "limits": [
        {
          "counter": "subscriptions_thread_mark_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 subscriptions_thread_mark

What does the subscriptions_thread_mark tool do? +

subscriptions_thread_mark. 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 subscriptions_thread_mark? +

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.

What risk level is subscriptions_thread_mark? +

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

Can I rate-limit subscriptions_thread_mark? +

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.

How do I block subscriptions_thread_mark completely? +

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.

What MCP server provides subscriptions_thread_mark? +

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.