update_memories · Engram MCP: Risk & Policy

WHAT IT DOES

What update_memories does on Engram

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

WHY IT NEEDS A POLICY

Why update_memories needs a policy

This tool creates or modifies data in the underlying SQLite database without permanently removing it. Updates are reversible through version history (available on this server as indicated by sibling tool 'get_history') and backups. While it operates on persistent memory, the operation itself is Write-category: data is changed but not destroyed, and can be rolled back or corrected.

From the tool's definition Tool name 'update_memories' and description 'Actualiza múltiples memorias en una sola transacción SQLite' (Updates multiple memories in a single SQLite transaction) indicate the tool modifies existing data reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_memories Rate-limited

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

FAQ

Questions about update_memories

What does the update_memories tool do? +

Actualiza múltiples memorias en una sola transacción SQLite. Informa cuáles se actualizaron y cuáles ids no se encontraron. It is categorised as a Write tool in the Engram MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_memories? +

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

What risk level is update_memories? +

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

Can I rate-limit update_memories? +

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

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

update_memories is provided by the Engram MCP server (jacksini/engram-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.