# memory_add

A write tool on the Agent-Memory-OS MCP server.

Agent View of the PolicyLayer registry record for `memory_add`. HTML page: https://policylayer.com/tools/agent-memory-os/memory-add

## Facts

- Tool: `memory_add`
- Server: Agent-Memory-OS (`yamantaka520/Agent-Memory-OS`) — https://policylayer.com/tools/agent-memory-os.md
- Homepage: https://github.com/yamantaka520/Agent-Memory-OS
- Risk category: Write (Medium risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "memory_add",
    "arguments": {}
  }
}
```

## Why memory_add is rated Medium

The 'add' verb indicates creation of new data records in the local-first memory engine. This is reversible (entries can be removed/edited), so Write rather than Destructive. Severity is medium because misuse could pollute shared team memory with false/malicious associations affecting multiple agents, but effects are not irreversible and no financial impact is evident.

From the tool's own definition: "Tool name 'memory_add' combined with server context (memory engine managing data for AI-agent teams) indicates data creation/insertion."

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Agent-Memory-OS:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "memory_add": {
      "limits": [
        {
          "counter": "memory_add_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Agent-Memory-OS (11)

- `memory_offload_context` — Other — https://policylayer.com/tools/agent-memory-os/memory-offload-context.md
- `memory_search` — Read — https://policylayer.com/tools/agent-memory-os/memory-search.md
- `memory_snapshot_diff` — Read — https://policylayer.com/tools/agent-memory-os/memory-snapshot-diff.md
- `memory_consolidate` — Write — https://policylayer.com/tools/agent-memory-os/memory-consolidate.md
- `memory_context_pack` — Write — https://policylayer.com/tools/agent-memory-os/memory-context-pack.md
- `memory_link` — Write — https://policylayer.com/tools/agent-memory-os/memory-link.md
- `memory_orchestrate_context` — Write — https://policylayer.com/tools/agent-memory-os/memory-orchestrate-context.md
- `memory_recall_feedback` — Write — https://policylayer.com/tools/agent-memory-os/memory-recall-feedback.md
- `memory_reload_context` — Write — https://policylayer.com/tools/agent-memory-os/memory-reload-context.md
- `memory_share` — Write — https://policylayer.com/tools/agent-memory-os/memory-share.md
- `memory_update` — Write — https://policylayer.com/tools/agent-memory-os/memory-update.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=agent-memory-os · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/agent-memory-os