Create a full backup of all memories as JSON file.
AI agents call backup to retrieve information from Nexus Memory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
A backup operation reads/exports all stored memories into a JSON file without modifying or deleting them. It is fundamentally a read/export operation. Severity is medium because it exports ALL memories in bulk, which could expose sensitive data if misused by an agent.
From the tool's definition "Create a full backup of all memories as JSON file"
Attacks that exploit this kind of access
Create a full backup of all memories as JSON file. It is categorised as a Read tool in the Nexus Memory MCP Server, which means it retrieves data without modifying state.
Register the Nexus Memory MCP server in PolicyLayer and add a rule for 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 Nexus Memory. Nothing to install.
backup 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 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 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.
backup is provided by the Nexus Memory MCP server (neboy72/nexus-memory). 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 →