Get statistics about all memories (counts, categories, tags, size, dates)
AI agents call get_statistics 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 queries and returns aggregate data about stored memories without modifying, deleting, or executing any operations. Statistics generation is a read-only operation that poses minimal risk even if misused by an AI agent, as it cannot alter state or access sensitive memory content beyond summary metadata.
From the tool's definition Tool name 'get_statistics' and description 'Get statistics about all memories (counts, categories, tags, size, dates)' indicate retrieval and aggregation of metadata with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get statistics about all memories (counts, categories, tags, size, dates). 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 get_statistics: 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.
get_statistics 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_statistics 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_statistics. 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_statistics is provided by the Claude Memory MCP Server MCP server (seongcheoljeon/claudememorymcp). 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 →