// SCAN REPORT

OpenSearch MCP Server

14 tools. 1 can modify or destroy data without limits.

1 write tool that can modify data. Rate limits recommended.

Last updated: 12 Jun 2026

1 can modify or destroy data

13 read-only

14 tools total

Community server · catalogue entry verified 12/06/2026

How to control OpenSearch MCP Server ↓

TOOL MAP

What OpenSearch MCP Server exposes to your agents

Read (13) Write / Execute (1) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous OpenSearch MCP Server tools

Execute · Medium search_documents While searching is primarily a read operation, 'custom query' implies the tool executes arbitrary query DSL against OpenSearch.

1 of OpenSearch MCP Server's 14 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control OpenSearch MCP Server

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

Cap read operations

{
  "get_cluster_health": {
    "limits": [
      {
        "counter": "get_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 OpenSearch 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 OPENSEARCH →

Free to start. No card required.

FULL CATALOGUE

All 14 OpenSearch MCP Server tools

EXECUTE 1 tools

Execute search_documents Search documents in an opensearch index with a custom query

READ 13 tools

Read get_cluster_health Get cluster health status Read get_cluster_stats Get cluster statistics Read get_hot_threads Check hot threads on nodes Read get_index_templates Get index template configurations Read get_ism_policies Get ISM policies and their configurations Read get_mapping Get index mapping Read get_recovery_status Get recovery status and estimated completion time Read get_settings Get index settings Read get_shard_allocation Get index shard allocation distribution Read get_tasks Get current tasks in cluster Read list_index_patterns List OpenSearch Dashboards index patterns2 Read list_indices List all indices in the Opensearch cluster Read generate_discover_url Generate OpenSearch Dashboards Discover view URL

FAQ

Questions about OpenSearch MCP Server

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

The OpenSearch MCP Server server is primarily read-only with 13 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 OpenSearch MCP Server MCP server expose? +

14 tools across 2 categories: Read, Write. 13 are read-only. 1 can modify, create, or delete data.

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

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

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

ENFORCE POLICY ON OPENSEARCH →

Free to start. No card required.

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