Search and filter historical transcripts. Options for method: 'semantic', 'keyword', 'date_range', 'related'.
AI agents call search_history to retrieve information from Chronicle 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 historical data with no side effects. It is purely a search/retrieval function operating on indexed chat logs stored locally. The various search methods (semantic, keyword, date-range filtering, related queries) are all read operations.
From the tool's definition Tool description explicitly states 'Search and filter historical transcripts' with options for querying ('semantic', 'keyword', 'date_range', 'related'). No mention of modification, deletion, execution, or financial operations.
Attacks that exploit this kind of access
Search and filter historical transcripts. Options for method: 'semantic', 'keyword', 'date_range', 'related'. It is categorised as a Read tool in the Chronicle MCP MCP Server, which means it retrieves data without modifying state.
Register the Chronicle 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 Chronicle 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 Chronicle MCP server (pypi:chronicle-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 →