Find all conversations and changes related to a specific file
AI agents call find_file_context 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 historical data about file-related conversations and changes from the Claude conversation history. It is purely informational and read-only, with no side effects, execution, or ability to modify underlying files or data. The blast radius of misuse is minimal — an attacker could only access conversation history they would likely already have access to.
From the tool's definition Tool description states it 'find[s] all conversations and changes related to a specific file' — retrieval and search operations with no modification, deletion, or execution capabilities.
Documented attack patterns abuse exactly the kind of access find_file_context 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 find_file_context:
{
"version": "1",
"default": "deny",
"tools": {
"find_file_context": {}
}
}find_file_context 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.
Find all conversations and changes related to a specific file. 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 find_file_context: 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.
find_file_context 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 find_file_context 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 find_file_context. 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.
find_file_context 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.