// SCAN REPORT

Knowledge Graph Memory Server

13 tools. 8 can modify or destroy data without limits.

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

Last updated: 11 Jun 2026

8 can modify or destroy data

5 read-only

13 tools total

Community server · catalogue entry verified 11/06/2026

How to control Knowledge Graph Memory Server ↓

TOOL MAP

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

MOST DANGEROUS TOOLS

Critical Risk

Destructive · High delete_entities This tool performs deletion of entities and relations, which is an irreversible destructive operation. Destructive · High delete_observations This tool permanently removes data (observations) that cannot be recovered. Destructive · High delete_relations This tool irreversibly removes data structures (relations) from a persistent knowledge graph. Write · Medium add_observations The tool adds (writes) new observations reversibly; users can later delete observations via the delete_observations sibling tool.

8 of Knowledge Graph Memory Server's 13 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

HOW TO CONTROL KNOWLEDGE GRAPH MEMORY SERVER

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

Deny destructive operations

{
  "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

{
  "add_observations": {
    "limits": [
      {
        "counter": "add_observations_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "find_similar_errors": {
    "limits": [
      {
        "counter": "find_similar_errors_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 Knowledge Graph Memory Server — 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 KNOWLEDGE GRAPH MEMORY →

Free to start. No card required.

ALL 13 KNOWLEDGE GRAPH MEMORY SERVER TOOLS

DESTRUCTIVE 3 tools

Destructive delete_entities Delete multiple entities and their associated relations from the knowledge graph Destructive delete_observations Delete specific observations from entities in the knowledge graph Destructive delete_relations Delete multiple relations from the knowledge graph

WRITE 5 tools

Write add_observations Add new observations to existing entities in the knowledge graph Write create_entities Create multiple new entities in the knowledge graph Write create_lesson Create a new lesson from an error and its solution Write create_relations Create multiple new relations between entities in the knowledge graph. Relations should be in active voice Write update_lesson_success Update the success rate of a lesson after applying its solution

READ 5 tools

RELATED SERVERS

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

FAQ

Can an AI agent delete data through the Knowledge Graph Memory Server MCP server? +

Yes. The Knowledge Graph Memory Server server exposes 3 destructive tools including delete_entities, delete_observations, 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 Knowledge Graph Memory Server? +

The Knowledge Graph Memory Server server has 5 write tools including add_observations, create_entities, create_lesson. 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 Knowledge Graph Memory Server.

How many tools does the Knowledge Graph Memory Server MCP server expose? +

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

How do I enforce a policy on Knowledge Graph Memory Server? +

Register the Knowledge Graph Memory Server 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 Knowledge Graph Memory Server tool call.

Deterministic rules across all 13 Knowledge Graph Memory Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON KNOWLEDGE GRAPH MEMORY →

Free to start. No card required.

13 Knowledge Graph Memory Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

Knowledge Graph Memory Server

// TOOL MAP

// MOST DANGEROUS TOOLS

// HOW TO CONTROL KNOWLEDGE GRAPH MEMORY SERVER

// ALL 13 KNOWLEDGE GRAPH MEMORY SERVER TOOLS

// RELATED SERVERS

// FAQ