Read the full conversation history of a thread. Returns thread metadata plus all messages in chronological order. Use offset/limit for long threads. Args: - project_id (string): The project ID - thread_id (string): The thread ID - offset (number, optional): Skip this many messages (default 0) - l...
AI agents call dialogue_read_thread to retrieve information from Claude Dialogue MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing data from a thread without modifying, deleting, or executing any operations. It is a straightforward data retrieval function with no destructive, financial, or execution capabilities. The low severity reflects minimal blast radius—an AI agent misusing this could access conversation history inappropriately, but cannot modify or delete data or trigger external actions.
From the tool's definition Tool description explicitly states "Read the full conversation history of a thread" and returns "thread metadata plus all messages in chronological order." The operation retrieves data with pagination controls (offset/limit) and produces no side effects.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Read the full conversation history of a thread. Returns thread metadata plus all messages in chronological order. Use offset/limit for long threads. Args: - project_id (string): The project ID - thread_id (string): The thread ID - offset (number, optional): Skip this many messages (default 0) - limit (number, optional): Max messages to return (default 50) Returns: Thread metadata and paginated message history. It is categorised as a Read tool in the Claude Dialogue MCP MCP Server, which means it retrieves data without modifying state.
Register the Claude Dialogue MCP server in PolicyLayer and add a rule for dialogue_read_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 Claude Dialogue MCP. Nothing to install.
dialogue_read_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 dialogue_read_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 dialogue_read_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.
dialogue_read_thread is provided by the Claude Dialogue MCP server (themethodolojeeorg/claude-dialogue-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 →