# memory_snapshot_diff

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

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

## Facts

- Tool: `memory_snapshot_diff`
- 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: Read (Low risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

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

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

## Why memory_snapshot_diff is rated Low

While the description is empty, the semantic meaning of 'diff' is to compare two states and output the differences. This is a read operation with no side effects. The tool name provides sufficient evidence despite the lack of explicit description. Confidence is moderately high but not higher due to the missing description and possibility the actual implementation could involve unexpected functionality.

From the tool's own definition: "The tool name 'memory_snapshot_diff' indicates comparison of memory snapshots. Diff operations are inherently read-only, comparing two states without modification."

## Use case

AI agents call memory_snapshot_diff to retrieve information from Agent-Memory-OS without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. 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_snapshot_diff": {}
  }
}
```

## 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_add` — Write — https://policylayer.com/tools/agent-memory-os/memory-add.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