AI agents use store_memory to create or update resources in Mentedb — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mentedb environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
tags | array | null | — | Optional tags for categorization |
scope | string | null | — | Memory scope: 'contextual' (default) = retrieved by semantic similarity. 'always' = returned on every process_turn call, regardless of conversation topic. |
content | string | Yes | The text content of the memory to store |
agent_id | string | null | — | Optional agent UUID that owns this memory (defaults to nil UUID) |
metadata | object | null | — | Optional key-value metadata |
memory_type | string | Yes | Memory type: episodic, semantic, procedural, anti_pattern, reasoning, or correction |
Parameters from the server's own tool schema.
The tool creates or modifies data (storing facts, preferences, decisions, corrections) in a reversible manner. It does not execute code, delete data irreversibly, or move money. While the stored content could theoretically influence agent behavior, the tool itself only writes data.
From the tool's definition Tool description explicitly states 'Store an important fact, preference, decision, or correction' with specified types (semantic, procedural, correction, anti_pattern). This is a create/write operation that persists data to the MenteDB memory store.
Risk signalsAccepts raw HTML/template content (content)
Attacks that exploit this kind of access
Store an important fact, preference, decision, or correction. Use types: semantic (facts), procedural (how-to), correction (fixes), anti_pattern (mistakes to avoid). Add tags for retrieval. It is categorised as a Write tool in the Mentedb MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
store_memory accepts 6 parameters: tags, scope, content, agent_id, metadata, memory_type. Required: content, memory_type. The full parameter table on this page comes from the server's own tool schema.
Register the Mentedb MCP server in PolicyLayer and add a rule for store_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 Mentedb. Nothing to install.
store_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 store_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 store_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.
store_memory is provided by the Mentedb MCP server (mentedb-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 →