Get statistics about the memory database
AI agents call get_memory_statistics to retrieve information from Claude Code Memory 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 the Neo4j database—a non-destructive read operation. It has no side effects, does not modify data, and does not execute code or commands. The blast radius of misuse is minimal, as an agent can only access statistical information about the database structure and content, not sensitive individual records or the ability to perform any mutations.
From the tool's definition Tool name 'get_memory_statistics' and description 'Get statistics about the memory database' indicate a query operation that retrieves aggregate data without modifying or executing actions.
Documented attack patterns abuse exactly the kind of access get_memory_statistics gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Code Memory Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_memory_statistics:
{
"version": "1",
"default": "deny",
"tools": {
"get_memory_statistics": {}
}
}get_memory_statistics 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 memory database. It is categorised as a Read tool in the Claude Code Memory Server MCP Server, which means it retrieves data without modifying state.
Register the Claude Code Memory Server MCP server in PolicyLayer and add a rule for get_memory_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 Code Memory Server. Nothing to install.
get_memory_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_memory_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_memory_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_memory_statistics is provided by the Claude Code Memory Server MCP server (viralv00d00/claude-code-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude Code Memory 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.
8 Claude Code Memory Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.