Search through Claude Code conversation history with smart insights
AI agents call search_conversations to retrieve information from Claude Historian 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 historical conversation data without modifying, deleting, or executing any operations. It is a pure read operation that returns information about past interactions. The low severity reflects minimal blast radius—an AI agent using this tool can only discover information already present in the conversation history, with no capability to alter data or trigger external operations.
From the tool's definition Tool description explicitly states it 'Search through Claude Code conversation history' with no mention of modification, deletion, or execution capabilities.
Documented attack patterns abuse exactly the kind of access search_conversations gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Historian, and nothing reaches the server without passing your rules. This is the rule we recommend for search_conversations:
{
"version": "1",
"default": "deny",
"tools": {
"search_conversations": {}
}
}search_conversations 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.
Search through Claude Code conversation history with smart insights. It is categorised as a Read tool in the Claude Historian MCP Server, which means it retrieves data without modifying state.
Register the Claude Historian MCP server in PolicyLayer and add a rule for search_conversations: 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 Historian. Nothing to install.
search_conversations 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 search_conversations 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 search_conversations. 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.
search_conversations is provided by the Claude Historian MCP server (vvkmnn/claude-historian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 9 Claude Historian tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
9 Claude Historian tools catalogued and risk-classified — across an index of 42,500+ MCP servers.