Store a new atomic fact in long-term memory. Use this whenever the user reveals durable preferences, facts about themselves, or context that should persist across sessions.
AI agents use memory_add to create or update resources in LedgerMem MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LedgerMem MCP Server environment.
This tool creates or modifies data (storing facts) in a reversible manner. It does not execute external operations, delete data irreversibly, move money, or read without side effects. Write category is appropriate.
From the tool's definition Tool name 'memory_add' and description state 'Store a new atomic fact in long-term memory', indicating creation of persistent data records.
Attacks that exploit this kind of access
Store a new atomic fact in long-term memory. Use this whenever the user reveals durable preferences, facts about themselves, or context that should persist across sessions. It is categorised as a Write tool in the LedgerMem MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LedgerMem MCP Server MCP server in PolicyLayer and add a rule for memory_add: 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 LedgerMem MCP Server. Nothing to install.
memory_add 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 memory_add 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 memory_add. 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.
memory_add is provided by the LedgerMem MCP Server MCP server (ledgermem/getmnemo-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 →