AI agents call get_thread_history to retrieve information from LangSmith MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The naming convention 'get_thread_history' and context within the LangSmith observability platform strongly suggests this retrieves historical conversation or thread data without modifying or deleting anything. This aligns with the Read category for data retrieval operations. Confidence is not higher due to the empty tool description, but the naming and server context provide sufficient evidence for classification.
From the tool's definition Tool name 'get_thread_history' indicates data retrieval; server description mentions 'fetching conversation history' as a core capability. No description provided for the specific tool, limiting confidence.
Documented attack patterns abuse exactly the kind of access get_thread_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LangSmith MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_thread_history:
{
"version": "1",
"default": "deny",
"tools": {
"get_thread_history": {}
}
}get_thread_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_thread_history. It is categorised as a Read tool in the LangSmith MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LangSmith MCP Server MCP server in PolicyLayer and add a rule for get_thread_history: 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 LangSmith MCP Server. Nothing to install.
get_thread_history 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_history 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_history. 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_history is provided by the LangSmith MCP Server MCP server (langchain-ai/langsmith-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from LangSmith MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
15 LangSmith MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.