memory_import_claude_md
AI agents use memory_import_claude_md to create or update resources in Claude Memory MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Memory MCP environment.
The tool appears to import data (likely from Claude markdown format based on the name) into a persistent memory store. This is a reversible write operation—data can be added/modified but also later deleted or corrected via memory_delete or other tools.
From the tool's definition Tool name contains 'import' and is paired with 'memory_export', suggesting it loads/persists data into the memory system. The server manages persistent, searchable per-project memory using DuckDB.
Attacks that exploit this kind of access
memory_import_claude_md. It is categorised as a Write tool in the Claude Memory MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Memory MCP server in PolicyLayer and add a rule for memory_import_claude_md: 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. Nothing to install.
memory_import_claude_md 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_import_claude_md 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_import_claude_md. 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_import_claude_md is provided by the Claude Memory MCP server (navid-kianfar/claude-memory-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 →