// SCAN REPORT

Search MCP

6 tools. 3 can modify or destroy data without limits.

3 write tools that can modify data. Rate limits recommended.

Last updated: 2 Jul 2026

3 can modify or destroy data

3 read-only

6 tools total

Community server · catalogue entry verified 02/07/2026

How to control Search MCP ↓

TOOL MAP

What Search MCP exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Search MCP tools

Write · Low create_ecommerce_test_index This tool creates (writes) a test index with sample data. Write · Low create_test_index This tool creates new data structures (Elasticsearch test indices) with sample documents. Write · Medium index_product Indexing a product in Elasticsearch creates or updates a document in the index, which is a write operation.

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

POLICY

How to control Search MCP

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

Rate limit write operations

{
  "create_ecommerce_test_index": {
    "limits": [
      {
        "counter": "create_ecommerce_test_index_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "search": {
    "limits": [
      {
        "counter": "search_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 Search 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 SEARCH →

Instant setup, no code required.

FULL CATALOGUE

All 6 Search MCP tools

WRITE 3 tools

Write create_ecommerce_test_index Create a test e-commerce index with sample products for demonstration purposes. Write create_test_index Create a test index with sample documents for demonstration purposes. Write index_product index_product

READ 3 tools

Read search search Read search_products_by_brand Search for products from a specific brand. Read search_products_by_category search_products_by_category

FAQ

Questions about Search MCP

How do I prevent bulk modifications through Search MCP? +

The Search MCP server has 3 write tools including create_ecommerce_test_index, create_test_index, index_product. 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 Search MCP.

How many tools does the Search MCP server expose? +

6 tools across 2 categories: Read, Write. 3 are read-only. 3 can modify, create, or delete data.

How do I enforce a policy on Search MCP? +

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

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

ENFORCE POLICY ON SEARCH →

Instant setup, no code required.

6 Search MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.