View memory system statistics: total memories, type distribution, domain distribution, cluster status, etc.
AI agents call memory_stats to retrieve information from Claude Persistent Memory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays statistics about the memory system (counts, distributions, status) with no side effects, data modifications, or external operations triggered. It is purely informational and poses minimal risk if misused by an AI agent.
From the tool's definition Tool name 'memory_stats' and description 'View memory system statistics' — uses read-only verb 'view' to retrieve aggregate statistics about the memory system without modifying, deleting, or executing operations.
Documented attack patterns abuse exactly the kind of access memory_stats gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Persistent Memory, and nothing reaches the server without passing your rules. This is the rule we recommend for memory_stats:
{
"version": "1",
"default": "deny",
"tools": {
"memory_stats": {}
}
}memory_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.
View memory system statistics: total memories, type distribution, domain distribution, cluster status, etc. It is categorised as a Read tool in the Claude Persistent Memory MCP Server, which means it retrieves data without modifying state.
Register the Claude Persistent Memory MCP server in PolicyLayer and add a rule for memory_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 Claude Persistent Memory. Nothing to install.
memory_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 memory_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 memory_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.
memory_stats is provided by the Claude Persistent Memory MCP server (mimi180306/claude-persistent-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude Persistent Memory, 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.
4 Claude Persistent Memory tools catalogued and risk-classified — across an index of 43,000+ MCP servers.