memory_load_from_folder
AI agents call memory_load_from_folder to retrieve information from Claude Memory MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name suggests loading/reading memory data from a folder into the system. No description is provided, which moderately reduces confidence, but the verb 'load' combined with the read-only nature of importing data from a folder indicates this is a Read operation with minimal blast radius—it retrieves or ingests data without deleting, modifying, executing code, or triggering financial actions.
From the tool's definition Tool name 'memory_load_from_folder' indicates a load/retrieval operation. The server context shows this is a memory management system with DuckDB storage. 'Load' semantics typically imply reading/importing data without modification of the source.
Attacks that exploit this kind of access
memory_load_from_folder. It is categorised as a Read tool in the Claude Memory MCP MCP Server, which means it retrieves data without modifying state.
Register the Claude Memory MCP server in PolicyLayer and add a rule for memory_load_from_folder: 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_load_from_folder is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the memory_load_from_folder 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_load_from_folder. 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_load_from_folder 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 →