Get recent memories from a session with pagination and filtering support
AI agents call zep_get_memory to retrieve information from Zep MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries existing memory data from a Zep Cloud session. The verbs 'get' and 'retrieve' combined with 'pagination and filtering support' indicate a read-only operation that does not create, modify, delete, or execute code. The low severity reflects minimal blast radius if misused by an agent — retrieving memories poses no destructive or financial risk.
From the tool's definition Tool name includes 'get' and description states 'Get recent memories from a session with pagination and filtering support' — purely retrieves data with no modification or side effects.
Attacks that exploit this kind of access
Get recent memories from a session with pagination and filtering support. It is categorised as a Read tool in the Zep MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Zep MCP Server MCP server in PolicyLayer and add a rule for zep_get_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.
zep_get_memory 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 zep_get_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.
Set action: deny in the PolicyLayer policy for zep_get_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.
zep_get_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.
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 →