AI agents use record_memory to create or update resources in Memory-Plus — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Memory-Plus environment.
This tool creates or stores new memory records in the local RAG store. It modifies state by adding data, but the operation is reversible (memories can be deleted or updated). It poses minimal blast radius—corrupted memory records would impair agent context but not destroy external systems or commit irreversible actions.
From the tool's definition Tool name 'record_memory' and server description indicating it 'enables recording...of persistent memories.' The empty tool description reduces confidence slightly, but the semantic intent is clear: recording persists data reversibly.
Documented attack patterns abuse exactly the kind of access record_memory gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Memory-Plus, and nothing reaches the server without passing your rules. This is the rule we recommend for record_memory:
{
"version": "1",
"default": "deny",
"tools": {
"record_memory": {
"limits": [
{
"counter": "record_memory_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}record_memory stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
record_memory. It is categorised as a Write tool in the Memory-Plus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Memory-Plus MCP server in PolicyLayer and add a rule for record_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 Memory-Plus. Nothing to install.
record_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 record_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 record_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.
record_memory is provided by the Memory-Plus MCP server (yuchen20/memory-plus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 Memory-Plus tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
14 Memory-Plus tools catalogued and risk-classified — across an index of 42,500+ MCP servers.