Get statistics about the memory store
AI agents call memory_stats to retrieve information from Claude Memory 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 retrieves statistics from an existing memory store. It has no side effects, does not modify data, and does not execute code or trigger external operations. It is purely informational and aligns with the Read category (retrieves or queries data; no side effects).
From the tool's definition Tool name is 'memory_stats' and description states 'Get statistics about the memory store' — this is a query operation that retrieves metadata without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Get statistics about the memory store. It is categorised as a Read tool in the Claude Memory MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Claude Memory MCP Server 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 Memory MCP Server. 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 Memory MCP Server MCP server (towan912/claude-memory-mcp-cf). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →