AI agents call threads_get_view to retrieve information from Slack without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves thread view data from Slack without modifying or deleting anything. It falls squarely into the Read category. Severity is medium rather than low because: (1) it accesses an undocumented endpoint, suggesting potential bypass of normal access controls or rate limits; (2) thread data may contain sensitive conversations; (3) bulk access to threads across a workspace could enable information gathering…
From the tool's definition Tool name 'threads_get_view' and description 'Get thread view data' indicate retrieval of Slack thread information. The phrase 'undocumented session endpoint' suggests access to internal/session-specific data rather than standard API endpoints.
Attacks that exploit this kind of access
Get thread view data (undocumented session endpoint). 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 threads_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.
threads_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 threads_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 threads_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.
threads_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.
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 →