// SCAN REPORT

Embeddings Searcher

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

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

Last updated: 4 Jul 2026

0 can modify or destroy data

4 read-only

4 tools total

Community server · catalogue entry verified 04/07/2026

How to control Embeddings Searcher ↓

TOOL MAP

What Embeddings Searcher 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 Embeddings Searcher

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

Cap read operations

{
  "get_document": {
    "limits": [
      {
        "counter": "get_document_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 Embeddings Searcher — 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 EMBEDDINGS SEARCHER →

Instant setup, no code required.

FULL CATALOGUE

All 4 Embeddings Searcher tools

READ 4 tools

Read get_document Retrieve the content of a specific document by path. Supports pagination to avoid overwhelming responses. Read get_stats Get indexing statistics (repositories, documents, chunks) Read list_repos List all indexed repositories Read search_docs Search through documentation using semantic similarity matching. Returns relevant document chunks with context

FAQ

Questions about Embeddings Searcher

Is the Embeddings Searcher MCP server safe to use without restrictions? +

The Embeddings Searcher 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 Embeddings Searcher 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 Embeddings Searcher? +

Register the Embeddings Searcher 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 Embeddings Searcher tool call.

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

ENFORCE POLICY ON EMBEDDINGS SEARCHER →

Instant setup, no code required.

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

// WHERE THIS COMES FROM

These policies come from Embeddings Searcher's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →