restore · Nexus Memory MCP: Risk & Policy

WHAT IT DOES

What restore does on Nexus Memory

AI agents use restore to create or update resources in Nexus Memory — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nexus Memory environment.

WHY IT NEEDS A POLICY

Why restore needs a policy

Restoring from backup is a Write operation because it creates or modifies data (memories) in a reversible manner. It's not Destructive because the original backup persists and the operation can be undone via another backup/restore cycle.

From the tool's definition Tool 'restore' loads and applies memories from a backup JSON file, which modifies the agent's persistent memory state. Description indicates it writes/overwrites memory data from an external source.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

restore Rate-limited

restore stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "restore": {
      "limits": [
        {
          "counter": "restore_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Nexus Memory, so you can run agents against it safely.

FAQ

Questions about restore

What does the restore tool do? +

Restore memories from a backup JSON file. It is categorised as a Write tool in the Nexus Memory MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on restore? +

Register the Nexus Memory MCP server in PolicyLayer and add a rule for restore: 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.

What risk level is restore? +

restore is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit restore? +

Yes. Add a rate_limit block to the restore 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.

How do I block restore completely? +

Set action: deny in the PolicyLayer policy for restore. 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.

What MCP server provides restore? +

restore 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.