// SCAN REPORT

Elasticsearch MCP Server

4 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated: 3 Jul 2026

0 can modify or destroy data

4 read-only

4 tools total

Community server · catalogue entry verified 03/07/2026

How to control Elasticsearch MCP Server ↓

TOOL MAP

What Elasticsearch MCP Server exposes to your agents

Read (4) Write / Execute (0) Destructive / Financial (0)

Running more than one server? Check your whole stack →

THE RISK

What can go wrong

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

POLICY

How to control Elasticsearch MCP Server

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

Cap read operations

{
  "es_cluster_health": {
    "limits": [
      {
        "counter": "es_cluster_health_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 MCP 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 ELASTICSEARCH →

Instant setup, no code required.

FULL CATALOGUE

All 4 Elasticsearch MCP Server tools

READ 4 tools

Read es_cluster_health Get Elasticsearch cluster health status, number of nodes, shards, and indices Read es_cluster_info Get Elasticsearch cluster information including version, name, and tagline Read es_index_list List all Elasticsearch indices with their health, status, document count, and storage size Read es_search Execute an Elasticsearch search query using the full Search API body. Pass the complete request body as you wo

FAQ

Questions about Elasticsearch MCP Server

Is the Elasticsearch MCP Server MCP server safe to use without restrictions? +

The Elasticsearch MCP Server server is primarily read-only with 4 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Elasticsearch MCP Server MCP server expose? +

4 tools across 1 categories: Read. 4 are read-only. 0 can modify, create, or delete data.

How do I enforce a policy on Elasticsearch MCP Server? +

Register the Elasticsearch MCP 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 Elasticsearch MCP Server tool call.

Deterministic rules across all 4 Elasticsearch MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON ELASTICSEARCH →

Instant setup, no code required.

4 Elasticsearch MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.