subscriptions_thread_get_view
A read tool on the Slack MCP server.
This record as markdown: /tools/karbassi-slack-mcp/subscriptions-thread-get-view.md
What subscriptions_thread_get_view does on Slack
AI agents call subscriptions_thread_get_view to retrieve information from Slack without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why subscriptions_thread_get_view is rated Low
The tool name structure ('get_view') clearly indicates a read operation that retrieves data without modification. However, without a description, there is some uncertainty about what specific data is accessed and whether it might include sensitive information like thread contents or user subscriptions.
From the tool's definition Tool name 'subscriptions_thread_get_view' includes 'get_view' which indicates retrieval/query of data. The 'subscriptions_thread' context suggests it retrieves subscription or thread-related information from Slack.
Attacks that exploit this kind of access
The rule that runs subscriptions_thread_get_view 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_get_view, this is the rule to start with:
subscriptions_thread_get_view is read-only, so it stays allowed. 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_get_view call is checked against it from then on.
Questions about subscriptions_thread_get_view
subscriptions_thread_get_view is a read tool on the Slack MCP server. It is categorised as a Read tool in the Slack MCP Server, which means it retrieves data without modifying state.
Register the Slack MCP server in PolicyLayer and add a rule for subscriptions_thread_get_view: 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_get_view is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the subscriptions_thread_get_view 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_get_view. 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_get_view 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