Given a message timestamp, retrieve the full conversation thread including all replies. Useful for understanding the context around a specific piece of feedback.
AI agents call get_thread_context to retrieve information from Slack Feedback MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a data retrieval operation that queries existing Slack conversation threads. It has no side effects beyond fetching information. While it accesses potentially sensitive team conversations, it remains in the Read category as it only queries and returns data without creating, modifying, or deleting anything.
From the tool's definition The tool retrieves and queries data—specifically retrieving 'the full conversation thread including all replies' given a message timestamp. It performs a read-only lookup operation with no stated capability to modify, delete, or execute actions.
Attacks that exploit this kind of access
Given a message timestamp, retrieve the full conversation thread including all replies. Useful for understanding the context around a specific piece of feedback. It is categorised as a Read tool in the Slack Feedback MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Slack Feedback MCP Server MCP server in PolicyLayer and add a rule for get_thread_context: 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 Feedback MCP Server. Nothing to install.
get_thread_context 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 get_thread_context 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 get_thread_context. 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.
get_thread_context is provided by the Slack Feedback MCP Server MCP server (nmontoro44/slack-feedback-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 →