remember_update_memory · Remember MCP: Risk & Policy

WHAT IT DOES

What remember_update_memory does on Remember

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

WHY IT NEEDS A POLICY

Why remember_update_memory needs a policy

This tool modifies existing records (memories) by updating fields and incrementing version numbers. It is reversible via version history and does not delete or overwrite data irreversibly. It falls squarely into the Write category.

From the tool's definition Tool name 'remember_update_memory' combined with description stating it 'Update[s] an existing memory with partial updates' and 'Only provided fields are updated'. This is a modification operation that creates new versions without deleting data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

remember_update_memory Rate-limited

remember_update_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": {
    "remember_update_memory": {
      "limits": [
        {
          "counter": "remember_update_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 Remember, so you can run agents against it safely.

FAQ

Questions about remember_update_memory

What does the remember_update_memory tool do? +

Update an existing memory with partial updates. Supports updating any field except id, user_id, doc_type, created_at. Version number is automatically incremented and updated_at is set. Only provided fields are updated (partial updates supported). Examples: -. It is categorised as a Write tool in the Remember MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on remember_update_memory? +

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

What risk level is remember_update_memory? +

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

Can I rate-limit remember_update_memory? +

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

Set action: deny in the PolicyLayer policy for remember_update_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 remember_update_memory? +

remember_update_memory is provided by the Remember MCP server (@prmichaelsen/remember-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.