Retrieve a complete thread conversation including all messages. This tool fetches the full context of a discussion, showing the thread metadata and every message posted in chronological order. Essential for understanding the complete conversation history. Example response: Thread:
AI agents call get_thread to retrieve information from Twist without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing thread data and message history without any side effects or mutations. It returns information only, fitting the Read category. Severity is low because unauthorized access to thread content, while a potential privacy concern, does not directly enable destructive, financial, or operational harm at the infrastructure level.
From the tool's definition Tool name 'get_thread' and description states 'Retrieve a complete thread conversation' and 'fetches the full context' — core retrieval operations with no modification, deletion, or execution.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Retrieve a complete thread conversation including all messages. This tool fetches the full context of a discussion, showing the thread metadata and every message posted in chronological order. Essential for understanding the complete conversation history. Example response: Thread:. It is categorised as a Read tool in the Twist MCP Server, which means it retrieves data without modifying state.
Register the Twist MCP server in PolicyLayer and add a rule for get_thread: 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 Twist. Nothing to install.
get_thread 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 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. 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 is provided by the Twist MCP server (twist-mcp-server). 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 →