AI agents use memory_reflect to create or update resources in Mementos — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mementos environment.
This tool creates new memory entries (lessons learned) based on reflection analysis. It modifies the memory state by adding new linked memories, making it a Write operation. It is reversible via the bulk_forget or entity_delete tools available on the same server.
From the tool's definition Tool writes structured lessons back as linked memories to the memory system. Described as 'write structured lessons back as linked memories' with a dry_run option for preview, indicating data creation/modification.
Attacks that exploit this kind of access
Reflect on a session, task, or range with an LLM-judge critic and write structured lessons back as linked memories. Use dry_run=true to preview. It is categorised as a Write tool in the Mementos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mementos MCP server in PolicyLayer and add a rule for memory_reflect: 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 Mementos. Nothing to install.
memory_reflect is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the memory_reflect 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 memory_reflect. 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.
memory_reflect is provided by the Mementos MCP server (@hasna/mementos). 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 →