Import memories from JSON file. Can skip or overwrite existing memories.
AI agents use import_memories to create or update resources in Claude Memory MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Memory MCP Server environment.
The tool creates or modifies data in the memory store by importing and potentially overwriting existing memories. This is reversible (memories can be edited or deleted later via other tools like delete_memory), so it falls under Write rather than Destructive.
From the tool's definition Tool description states it can 'Import memories from JSON file' and 'skip or overwrite existing memories.' The ability to overwrite existing data indicates modification of stored data.
Attacks that exploit this kind of access
Import memories from JSON file. Can skip or overwrite existing memories. It is categorised as a Write tool in the Claude Memory MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Memory MCP Server MCP server in PolicyLayer and add a rule for import_memories: 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 Claude Memory MCP Server. Nothing to install.
import_memories 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 import_memories 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 import_memories. 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.
import_memories is provided by the Claude Memory MCP Server MCP server (seongcheoljeon/claudememorymcp). 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 →