Store a new memory with rich metadata context (file, git, function).
AI agents use remember_with_context to create or update resources in memro MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your memro MCP Server environment.
This tool writes new data (memories with metadata) to persistent storage. It is reversible in the sense that a sibling tool 'delete_memory' exists, making this a Write rather than Destructive action. Misuse could lead to injection of false or misleading context into the AI's long-term memory, hence medium severity.
From the tool's definition 'Store a new memory with rich metadata context' — creates a new memory entry with associated metadata
Attacks that exploit this kind of access
Store a new memory with rich metadata context (file, git, function). It is categorised as a Write tool in the memro MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the memro MCP Server MCP server in PolicyLayer and add a rule for remember_with_context: 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 memro MCP Server. Nothing to install.
remember_with_context 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_with_context 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_with_context. 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_with_context is provided by the memro MCP Server MCP server (memrohq/memro-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 →