// SCAN REPORT

Zep MCP Server

7 tools. 1 can modify or destroy data without limits.

1 write tool that can modify data. Rate limits recommended.

Last updated: 4 Jul 2026

1 can modify or destroy data

6 read-only

7 tools total

Community server · catalogue entry verified 04/07/2026

How to control Zep MCP Server ↓

TOOL MAP

What Zep MCP Server exposes to your agents

Read (6) Write / Execute (1) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Zep MCP Server tools

Write · Medium zep_store_memory This tool creates/writes new memory data to Zep Cloud for a session.

1 of Zep MCP Server's 7 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Zep MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Zep MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "zep_store_memory": {
    "limits": [
      {
        "counter": "zep_store_memory_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "zep_get_graph_edges": {
    "limits": [
      {
        "counter": "zep_get_graph_edges_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Zep MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON ZEP →

Instant setup, no code required.

FULL CATALOGUE

All 7 Zep MCP Server tools

WRITE 1 tools

Write zep_store_memory Store information in Zep Cloud memory for a specific session

READ 6 tools

Read zep_get_graph_edges Get all edges (relationships) from the user knowledge graph Read zep_get_graph_nodes Get all nodes (entities) from the user knowledge graph Read zep_get_memory Get recent memories from a session with pagination and filtering support Read zep_get_node_details Get detailed information about a specific node including its edges and episodes Read zep_get_thread_context Get relevant context from ALL past threads based on recent messages in current thread. Automatically pulls in Read zep_search_memory Search Zep Cloud memory in a specific session

FAQ

Questions about Zep MCP Server

How do I prevent bulk modifications through Zep MCP Server? +

The Zep MCP Server server has 1 write tools including zep_store_memory. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Zep MCP Server.

How many tools does the Zep MCP Server MCP server expose? +

7 tools across 1 categories: Read. 6 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on Zep MCP Server? +

Register the Zep MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Zep MCP Server tool call.

Deterministic rules across all 7 Zep MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON ZEP →

Instant setup, no code required.

7 Zep MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.