zep_store_memory · Zep MCP Server MCP: Risk & Policy

WHAT IT DOES

What zep_store_memory does on Zep MCP Server

AI agents use zep_store_memory to create or update resources in Zep MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zep MCP Server environment.

WHY IT NEEDS A POLICY

Why zep_store_memory needs a policy

This tool creates/writes new memory data to Zep Cloud for a session. It is a reversible write operation (data can potentially be deleted or overwritten). Misuse could result in storing incorrect, misleading, or sensitive information that persists across conversations, hence medium severity.

From the tool's definition 'Store information in Zep Cloud memory for a specific session'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

zep_store_memory Rate-limited

zep_store_memory stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "zep_store_memory": {
      "limits": [
        {
          "counter": "zep_store_memory_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Zep MCP Server, so you can run agents against it safely.

FAQ

Questions about zep_store_memory

What does the zep_store_memory tool do? +

Store information in Zep Cloud memory for a specific session. It is categorised as a Write tool in the Zep MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on zep_store_memory? +

Register the Zep MCP Server MCP server in PolicyLayer and add a rule for zep_store_memory: 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 Zep MCP Server. Nothing to install.

What risk level is zep_store_memory? +

zep_store_memory is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit zep_store_memory? +

Yes. Add a rate_limit block to the zep_store_memory 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 zep_store_memory completely? +

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

zep_store_memory is provided by the Zep MCP Server MCP server (wastrilith2k/zep-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.