Create a new memory with optional template. Memories can store any type of information: notes, events, people, recipes, etc. Each memory has a weight (significance 0-1). Trust defaults to SECRET (level 5) and can be changed via remember_request_set_trust_level. Location and context are automatica...
AI agents use remember_create_memory to create or update resources in Remember — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Remember environment.
This tool creates and stores data reversibly in the Remember system. While it persists information, the operation is not destructive (memories can be modified or removed), and there are no financial or code execution implications.
From the tool's definition Tool description states 'Create a new memory' and allows storing 'any type of information: notes, events, people, recipes, etc.' with configurable weight and trust levels.
Attacks that exploit this kind of access
Create a new memory with optional template. Memories can store any type of information: notes, events, people, recipes, etc. Each memory has a weight (significance 0-1). Trust defaults to SECRET (level 5) and can be changed via remember_request_set_trust_level. Location and context are automatically captured from the request. IMPORTANT - Content vs Summary: - content: MUST be EXACT user-provided text. DO NOT paraphrase or modify. - summary: Use for AI-generated summaries or interpretations. - Example: User says. It is categorised as a Write tool in the Remember MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Remember MCP server in PolicyLayer and add a rule for remember_create_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 Remember. Nothing to install.
remember_create_memory 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 remember_create_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 remember_create_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.
remember_create_memory is provided by the Remember MCP server (@prmichaelsen/remember-mcp). 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 →