List all files that have local history entries in VS Code
AI agents call list_history_files 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 retrieves metadata about files with history entries without reading their contents, modifying data, or triggering side effects. It is a simple listing/browsing operation consistent with the Read category. Severity is low because exposure does not grant access to sensitive file contents themselves, only knowledge that certain files have been edited.
From the tool's definition Tool name is 'list_history_files' and description states 'List all files that have local history entries' — a straightforward query/enumeration operation with no modification or deletion capability.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access list_history_files 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 list_history_files:
{
"version": "1",
"default": "deny",
"tools": {
"list_history_files": {}
}
}list_history_files 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.
List all files that have local history entries in VS Code. 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 list_history_files: 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.
list_history_files 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 list_history_files 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 list_history_files. 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.
list_history_files 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.