Stores a new piece of information in the memory system. Automatically classifies the note type (rule, procedure, concept, tool, reference, integration), extracts metadata, and starts the linking and evolution process in the background.
AI agents use create_atomic_note to create or update resources in A-MEM: Agentic Memory System — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your A-MEM: Agentic Memory System environment.
This tool creates new records in a graph-based memory system. While reversible (notes can presumably be deleted via delete_atomic_note), it modifies the agent's persistent memory state and triggers background processes. The impact is constrained to information storage without destructive effects, financial transactions, or arbitrary code execution, making it Write rather than Execute or higher severity categories.
From the tool's definition Tool description states it 'Stores a new piece of information in the memory system' and 'starts the linking and evolution process in the background.' The verb 'Stores' combined with automatic classification and metadata extraction indicates data creation.
Documented attack patterns abuse exactly the kind of access create_atomic_note gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and A-MEM: Agentic Memory System, and nothing reaches the server without passing your rules. This is the rule we recommend for create_atomic_note:
{
"version": "1",
"default": "deny",
"tools": {
"create_atomic_note": {
"limits": [
{
"counter": "create_atomic_note_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_atomic_note 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.
Stores a new piece of information in the memory system. Automatically classifies the note type (rule, procedure, concept, tool, reference, integration), extracts metadata, and starts the linking and evolution process in the background. It is categorised as a Write tool in the A-MEM: Agentic Memory System MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the A-MEM: Agentic Memory System MCP server in PolicyLayer and add a rule for create_atomic_note: 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 A-MEM: Agentic Memory System. Nothing to install.
create_atomic_note 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 create_atomic_note 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 create_atomic_note. 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.
create_atomic_note is provided by the A-MEM: Agentic Memory System MCP server (tobs-code/a-mem-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from A-MEM: Agentic Memory System, 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 A-MEM: Agentic Memory System tools catalogued and risk-classified — across an index of 43,000+ MCP servers.