save_memories · Engram MCP: Risk & Policy

WHAT IT DOES

What save_memories does on Engram

AI agents use save_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 save_memories needs a policy

This tool creates or modifies data in a SQLite database by persisting multiple memory records in a single transaction. It is reversible (data can be deleted, modified, or updated later), making it a Write operation rather than Destructive.

From the tool's definition Tool name 'save_memories' and description 'Guarda múltiples memorias en una sola transacción SQLite' (saves multiple memories in a single SQLite transaction).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

save_memories Rate-limited

save_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": {
    "save_memories": {
      "limits": [
        {
          "counter": "save_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 save_memories

What does the save_memories tool do? +

Guarda múltiples memorias en una sola transacción SQLite. Ideal para bootstrapping de contexto masivo o guardar varias notas de golpe. Más eficiente que llamar save_memory repetidamente. 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 save_memories? +

Register the Engram MCP server in PolicyLayer and add a rule for save_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 save_memories? +

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

Can I rate-limit save_memories? +

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

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

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