restore_memory · Chronos MCP: Risk & Policy

WHAT IT DOES

What restore_memory does on Chronos MCP

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

WHY IT NEEDS A POLICY

Why restore_memory needs a policy

This tool modifies stored data (memories) by reversibly restoring previously forgotten entries. It creates or changes the state of memory records without permanent deletion or executing arbitrary operations. The action is reversible (memories can be forgotten again) and has no blast radius beyond altering what information is accessible within the local knowledge graph.

From the tool's definition restore_memory Un-forget a previously forgotten memory. It immediately reappears

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

restore_memory Rate-limited

restore_memory 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_memory": {
      "limits": [
        {
          "counter": "restore_memory_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 Chronos MCP, so you can run agents against it safely.

FAQ

Questions about restore_memory

What does the restore_memory tool do? +

Un-forget a previously forgotten memory. It immediately reappears. It is categorised as a Write tool in the Chronos MCP 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_memory? +

Register the Chronos MCP server in PolicyLayer and add a rule for restore_memory: 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 Chronos MCP. Nothing to install.

What risk level is restore_memory? +

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

Can I rate-limit restore_memory? +

Yes. Add a rate_limit block to the restore_memory 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_memory completely? +

Set action: deny in the PolicyLayer policy for restore_memory. 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_memory? +

restore_memory is provided by the Chronos MCP server (kodaxadev/chronosmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.