Advanced search with tags, languages, tools, date filters, and semantic search
AI agents call search_history to retrieve information from Claude Code History MCP 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 data without side effects. It searches existing conversation history and returns results—a classic read operation. The mention of 'advanced search' and 'semantic search' reinforces that it is a query/retrieval function. No evidence of creating, modifying, deleting, executing code, or financial transactions.
From the tool's definition Tool performs 'search' of conversation history with filters (tags, languages, tools, date) and 'semantic search' capabilities. No modification, deletion, or execution described.
Attacks that exploit this kind of access
Advanced search with tags, languages, tools, date filters, and semantic search. It is categorised as a Read tool in the Claude Code History MCP MCP Server, which means it retrieves data without modifying state.
Register the Claude Code History MCP server in PolicyLayer and add a rule for search_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 Claude Code History MCP. Nothing to install.
search_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 search_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 search_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.
search_history is provided by the Claude Code History MCP server (tim0120/claude-code-history-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 →