Low Risk

get_memory_stats

Get statistics about the memory store — total count, total characters, and storage path.

How to control get_memory_stats ↓

What get_memory_stats does on ContextKeep

AI agents call get_memory_stats to retrieve information from ContextKeep without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_memory_stats needs a policy

This tool queries and returns read-only statistics (counts, character totals, storage path) about the memory store without any side effects. It performs a retrieval operation comparable to a 'get' or 'fetch' action. The low severity reflects that misuse would only expose metadata about stored memories, not the memories themselves or system operations.

From the tool's definition Tool name 'get_memory_stats' and description 'Get statistics about the memory store — total count, total characters, and storage path' indicate retrieval of aggregate metadata only, with no modification, deletion, or execution of code.

Documented attack patterns abuse exactly the kind of access get_memory_stats gives an agent:

How to control get_memory_stats

PolicyLayer is an MCP gateway — it sits between your AI agents and ContextKeep, and nothing reaches the server without passing your rules. This is the rule we recommend for get_memory_stats:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_memory_stats": {}
  }
}

get_memory_stats is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register ContextKeep — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_memory_stats

What does the get_memory_stats tool do? +

Get statistics about the memory store — total count, total characters, and storage path. It is categorised as a Read tool in the ContextKeep MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_memory_stats? +

Register the ContextKeep MCP server in PolicyLayer and add a rule for get_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 ContextKeep. Nothing to install.

What risk level is get_memory_stats? +

get_memory_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_memory_stats? +

Yes. Add a rate_limit block to the get_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.

How do I block get_memory_stats completely? +

Set action: deny in the PolicyLayer policy for get_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.

What MCP server provides get_memory_stats? +

get_memory_stats is provided by the ContextKeep MCP server (mordang7/contextkeep). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every ContextKeep tool call.

Start from ContextKeep, 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 ContextKeep tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.