Get statistics about the local history (total files, entries, etc.)
AI agents call get_history_stats 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 queries and returns statistical information (counts, summaries) from the local history system. It has no side effects, does not modify data, does not execute code, and does not delete anything. It is purely informational and read-only, making it the safest category with low blast radius if misused by an AI agent.
From the tool's definition Tool name 'get_history_stats' and description 'Get statistics about the local history (total files, entries, etc.)' indicate it retrieves aggregate metadata about stored history without modifying, deleting, or executing operations.
Documented attack patterns abuse exactly the kind of access get_history_stats 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 get_history_stats:
{
"version": "1",
"default": "deny",
"tools": {
"get_history_stats": {}
}
}get_history_stats 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.
Get statistics about the local history (total files, entries, etc.). 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 get_history_stats: 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.
get_history_stats 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 get_history_stats 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 get_history_stats. 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.
get_history_stats 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.