Retrieve most recent memories by creation timestamp WHEN: You want to see what was recently learned, created, or discussed. Useful for getting context on recent work, reviewing recent decisions, or understanding what was added to memory recently. BEHAVIOR: Returns memories sorted by creation date...
AI agents call get_recent_memories to retrieve information from Forgetful without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query operation that retrieves and sorts existing memories by timestamp. It has no capability to create, modify, delete, or execute operations. The blast radius of misuse is minimal—an agent could only access historical memory data without causing harm to the system or data integrity.
From the tool's definition Tool description states 'Retrieve most recent memories' and 'Returns memories sorted by creation date'. The NOT-USE section clarifies this is for retrieval only, not modification. No side effects or data alteration occurs.
Documented attack patterns abuse exactly the kind of access get_recent_memories gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Forgetful, and nothing reaches the server without passing your rules. This is the rule we recommend for get_recent_memories:
{
"version": "1",
"default": "deny",
"tools": {
"get_recent_memories": {}
}
}get_recent_memories 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.
Retrieve most recent memories by creation timestamp WHEN: You want to see what was recently learned, created, or discussed. Useful for getting context on recent work, reviewing recent decisions, or understanding what was added to memory recently. BEHAVIOR: Returns memories sorted by creation date (newest first). Optionally filter to specific projects. Does not use semantic search - purely timestamp-based retrieval. Excludes obsolete memories. NOT-USE: Searching for specific topics (use query_memory), getting a specific memory by ID (use get_memory), or listing all memories without time constraints. Args: limit: Number of memories to return (1-100, default 10) project_ids: Optional filter to specific projects. Accepts array [1] or [1, 3] for multiple Returns: List of Memory objects sorted by created_at DESC (newest first). It is categorised as a Read tool in the Forgetful MCP Server, which means it retrieves data without modifying state.
Register the Forgetful MCP server in PolicyLayer and add a rule for get_recent_memories: 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 Forgetful. Nothing to install.
get_recent_memories 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_recent_memories 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_recent_memories. 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_recent_memories is provided by the Forgetful MCP server (scottrbk/forgetful). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 59 Forgetful tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
59 Forgetful tools catalogued and risk-classified — across an index of 42,500+ MCP servers.