Create a backup of all memories
AI agents use create_backup 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.
Backup creation is a Write operation—it creates new data (backup copies) without irreversibly removing or overwriting existing data. The blast radius is low because backups are typically protective operations that do not directly modify production data or cause financial harm. Confidence is high because the intent is unambiguous from both name and description.
From the tool's definition Tool name 'create_backup' and description 'Create a backup of all memories' indicate the tool creates a copy of data without deleting or modifying the original memories. This is a reversible data creation operation.
Attacks that exploit this kind of access
Create a backup of all 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 create_backup: 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.
create_backup 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 create_backup 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 create_backup. 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.
create_backup 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 →