// SCAN REPORT

N2n Memory

12 tools. 7 can modify or destroy data without limits.

3 destructive tools with no built-in limits. Policy required.

Last updated: 12 Jun 2026

7 can modify or destroy data

5 read-only

12 tools total

Community server · catalogue entry verified 12/06/2026

How to control N2n Memory ↓

TOOL MAP

What N2n Memory exposes to your agents

Read (5) Write / Execute (4) Destructive / Financial (3)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous N2n Memory tools

Destructive · High n2n_delete_entities Delete operations are irreversible and permanently remove data from the knowledge graph. Destructive · High n2n_delete_observations The 'delete' verb combined with 'observations' (data records in a knowledge graph) makes this a Destructive operation that cannot be undone. Destructive · High n2n_delete_relations The tool performs an irreversible deletion operation on graph relations. Write · Medium n2n_add_entities The 'add_entities' operation creates or inserts new data (entities) into a persisted knowledge graph within a project directory.

7 of N2n Memory's 12 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control N2n Memory

PolicyLayer is an MCP gateway — it sits between your AI agents and N2n Memory, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "n2n_delete_entities": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "n2n_add_entities": {
    "limits": [
      {
        "counter": "n2n_add_entities_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "n2n_get_graph_summary": {
    "limits": [
      {
        "counter": "n2n_get_graph_summary_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register N2n Memory — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON N2N MEMORY →

Free to start. No card required.

FULL CATALOGUE

All 12 N2n Memory tools

DESTRUCTIVE 3 tools

Destructive n2n_delete_entities n2n_delete_entities Destructive n2n_delete_observations n2n_delete_observations Destructive n2n_delete_relations n2n_delete_relations

WRITE 4 tools

Write n2n_add_entities n2n_add_entities Write n2n_add_observations n2n_add_observations Write n2n_create_relations n2n_create_relations Write n2n_update_context n2n_update_context

READ 5 tools

Read n2n_get_graph_summary n2n_get_graph_summary Read n2n_read_graph n2n_read_graph Read n2n_search n2n_search Read n2n_export_markdown n2n_export_markdown Read n2n_open_nodes n2n_open_nodes

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about N2n Memory

Can an AI agent delete data through the N2n Memory MCP server? +

Yes. The N2n Memory server exposes 3 destructive tools including n2n_delete_entities, n2n_delete_observations, n2n_delete_relations. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through N2n Memory? +

The N2n Memory server has 4 write tools including n2n_add_entities, n2n_add_observations, n2n_create_relations. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach N2n Memory.

How many tools does the N2n Memory MCP server expose? +

12 tools across 3 categories: Destructive, Read, Write. 5 are read-only. 7 can modify, create, or delete data.

How do I enforce a policy on N2n Memory? +

Register the N2n Memory MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every N2n Memory tool call.

Deterministic rules across all 12 N2n Memory tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON N2N MEMORY →

Free to start. No card required.

12 N2n Memory tools catalogued and risk-classified — across an index of 43,000+ MCP servers.