// SCAN REPORT

Elasticsearch Knowledge Graph for MCP

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

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

Last updated: 11 Jun 2026

13 can modify or destroy data

10 read-only

23 tools total

Community server · catalogue entry verified 11/06/2026

How to control Elasticsearch Knowledge Graph for MCP ↓

TOOL MAP

What Elasticsearch Knowledge Graph for MCP exposes to your agents

Read (10) Write / Execute (8) Destructive / Financial (5)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Elasticsearch Knowledge Graph for MCP tools

Destructive · High delete_entities This tool permanently removes entities and their associations from the knowledge graph without reversibility. Destructive · High delete_observations This tool permanently removes observations, which cannot be undone. Destructive · High delete_relations This tool permanently removes data (relation records) from the knowledge graph, which constitutes an irreversible, destructive action. Destructive · High delete_zone This tool performs irreversible deletion of potentially large amounts of stored data (entire zones including entities and relations).

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

POLICY

How to control Elasticsearch Knowledge Graph for MCP

PolicyLayer is an MCP gateway — it sits between your AI agents and Elasticsearch Knowledge Graph for MCP, 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

{
  "get_recent": {
    "limits": [
      {
        "counter": "get_recent_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 Elasticsearch Knowledge Graph for MCP — 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 ELASTICSEARCH KNOWLEDGE GRAPH FOR →

Free to start. No card required.

FULL CATALOGUE

All 23 Elasticsearch Knowledge Graph for MCP tools

DESTRUCTIVE 5 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 Destructive delete_zone Delete a memory zone and all its entities/relations. Destructive move_entities Move entities between zones (copy + delete from source).

WRITE 8 tools

Write add_observations Add new observations to existing entities in the knowledge graph Write copy_entities Copy entities between zones with optional relation handling. Write create_entities Create multiple new entities in the knowledge graph Write create_relations Create multiple new relations between entities in the knowledge graph. Relations should be in active voice Write create_zone Create a new memory zone with optional description. Write mark_important Mark entity as important in knowledge graph (memory) by boosting its relevance score Write merge_zones Merge multiple zones with conflict resolution options. Write update_entities Update entities in knowledge graph (memory)

READ 10 tools

Read get_recent Get recently accessed entities from knowledge graph (memory) and their relations Read get_time_utc Get the current UTC time in YYYY-MM-DD hh:mm:ss format Read inspect_files Agent driven file inspection that uses AI to retrieve relevant content from multiple files. Read inspect_knowledge_graph Agent driven knowledge graph inspection that uses AI to retrieve relevant entities and relations. Results incl Read list_zones List all available memory zones with metadata. When a reason is provided, zones will be filtered and prioritiz Read read_graph Read the entire knowledge graph Read search_nodes Search for nodes in the knowledge graph based on a query Read verify_entity Explicitly verify that an entity Read zone_stats Get statistics for entities and relationships in a zone. Read open_nodes Open specific nodes in the knowledge graph by their names

EXPLORE

Related servers

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

FAQ

Questions about Elasticsearch Knowledge Graph for MCP

Can an AI agent delete data through the Elasticsearch Knowledge Graph for MCP server? +

Yes. The Elasticsearch Knowledge Graph for MCP server exposes 5 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 Elasticsearch Knowledge Graph for MCP? +

The Elasticsearch Knowledge Graph for MCP server has 8 write tools including add_observations, copy_entities, create_entities. 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 Elasticsearch Knowledge Graph for MCP.

How many tools does the Elasticsearch Knowledge Graph for MCP server expose? +

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

How do I enforce a policy on Elasticsearch Knowledge Graph for MCP? +

Register the Elasticsearch Knowledge Graph for 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 Elasticsearch Knowledge Graph for MCP tool call.

Deterministic rules across all 23 Elasticsearch Knowledge Graph for MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON ELASTICSEARCH KNOWLEDGE GRAPH FOR →

Free to start. No card required.

23 Elasticsearch Knowledge Graph for MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.