Search for specific content across all history entries
AI agents call search_history_content to retrieve information from Local History MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only searches and retrieves historical file content. It has no side effects, does not modify data, does not execute code, does not delete anything, and does not involve financial operations. The blast radius of misuse is minimal—an AI agent could search for sensitive information in local history, but cannot change or harm the system. This is a pure read operation.
From the tool's definition Tool performs 'Search for specific content across all history entries' - a query operation that retrieves data from history snapshots without modifying, deleting, or executing anything.
Documented attack patterns abuse exactly the kind of access search_history_content gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Local History MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_history_content:
{
"version": "1",
"default": "deny",
"tools": {
"search_history_content": {}
}
}search_history_content 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 for specific content across all history entries. It is categorised as a Read tool in the Local History MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Local History MCP Server MCP server in PolicyLayer and add a rule for search_history_content: 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 Local History MCP Server. Nothing to install.
search_history_content 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_content 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_content. 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_content is provided by the Local History MCP Server MCP server (xxczaki/local-history-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Local History 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.
6 Local History MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.