Save a memory to MNEMOS. Category: infrastructure/solutions/patterns/decisions/projects/standards.
AI agents use mnemos.memory_create to create or update resources in Mnemos — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mnemos environment.
This tool creates and stores new data in a persistent memory system. Creation of data is a Write operation. Severity is medium because misuse could clutter the memory system or store sensitive/incorrect information, but the effects are reversible (memories can presumably be deleted or corrected).
From the tool's definition Tool is named 'memory_create' and described as 'Save a memory to MNEMOS', which indicates creation of persistent data in a memory storage system.
Documented attack patterns abuse exactly the kind of access mnemos.memory_create gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mnemos, and nothing reaches the server without passing your rules. This is the rule we recommend for mnemos.memory_create:
{
"version": "1",
"default": "deny",
"tools": {
"mnemos.memory_create": {
"limits": [
{
"counter": "mnemos.memory_create_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}mnemos.memory_create 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.
Save a memory to MNEMOS. Category: infrastructure/solutions/patterns/decisions/projects/standards. It is categorised as a Write tool in the Mnemos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mnemos MCP server in PolicyLayer and add a rule for mnemos.memory_create: 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 Mnemos. Nothing to install.
mnemos.memory_create 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 mnemos.memory_create 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 mnemos.memory_create. 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.
mnemos.memory_create is provided by the Mnemos MCP server (ncz-os/mnemos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mnemos, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
15 Mnemos tools catalogued and risk-classified — across an index of 43,000+ MCP servers.