// SCAN REPORT

Meilisearch MCP Server

68 tools. 38 can modify or destroy data without limits.

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

Last updated:

38 can modify or destroy data
30 read-only
68 tools total
// TOOL MAP
Read (30) Write / Execute (19) Destructive / Financial (19)
// WHAT CAN GO WRONG
✕

Destructive tools (cancel-tasks, delete-all-documents, delete-document) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.

✕

Write operations (add-documents, create-index, enable-vector-search) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.

✕

Execute tools (wait-for-task) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.

// RECOMMENDED RULES
Deny destructive operations
cancel-tasks:
  rules:
    - action: deny

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
add-documents:
  rules:
    - rate_limit: 30/hour

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
facet-search:
  rules:
    - rate_limit: 60/minute

Controls API costs and prevents retry loops from exhausting upstream rate limits.

// ALL 68 MEILISEARCH MCP SERVER TOOLS
DESTRUCTIVE 19 tools
Destructive cancel-tasks Destructive delete-all-documents Destructive delete-document Destructive delete-documents Destructive delete-index Destructive delete-tasks Destructive reset-displayed-attributes Destructive reset-distinct-attribute Destructive reset-embedders Destructive reset-faceting Destructive reset-filterable-attributes Destructive reset-pagination Destructive reset-ranking-rules Destructive reset-searchable-attributes Destructive reset-settings Destructive reset-sortable-attributes Destructive reset-stop-words Destructive reset-synonyms Destructive reset-typo-tolerance
EXECUTE 1 tools
Execute wait-for-task
WRITE 18 tools
Write add-documents Write create-index Write enable-vector-search Write update-displayed-attributes Write update-distinct-attribute Write update-documents Write update-embedders Write update-faceting Write update-filterable-attributes Write update-index Write update-pagination Write update-ranking-rules Write update-searchable-attributes Write update-settings Write update-sortable-attributes Write update-stop-words Write update-synonyms Write update-typo-tolerance
READ 30 tools
Read facet-search Read get-displayed-attributes Read get-distinct-attribute Read get-document Read get-documents Read get-embedders Read get-experimental-features Read get-faceting Read get-filterable-attributes Read get-index Read get-pagination Read get-ranking-rules Read get-searchable-attributes Read get-settings Read get-sortable-attributes Read get-stop-words Read get-synonyms Read get-task Read get-tasks Read get-typo-tolerance Read health Read info Read list-indexes Read list-tasks Read multi-search Read search Read stats Read swap-indexes Read vector-search Read version
// FAQ
Can an AI agent delete data through the Meilisearch MCP Server MCP server? +

Yes. The Meilisearch MCP Server server exposes 19 destructive tools including cancel-tasks, delete-all-documents, delete-document. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Meilisearch MCP Server? +

The Meilisearch MCP Server server has 18 write tools including add-documents, create-index, enable-vector-search. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.

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

68 tools across 4 categories: Destructive, Execute, Read, Write. 30 are read-only. 38 can modify, create, or delete data.

How do I add Intercept to my Meilisearch MCP Server setup? +

One line change. Instead of running the Meilisearch MCP Server server directly, prefix it with Intercept: intercept -c devlimelabs-meilisearch-ts-mcp.yaml -- npx -y @devlimelabs/meilisearch-ts-mcp. Download a pre-built policy from policylayer.com/policies/devlimelabs-meilisearch-ts-mcp and adjust the limits to match your use case.

// RELATED SERVERS

Other MCP servers with similar tools.

Starter policies available for each. Same risk classification, same one-command setup.

Mcp Api 314 tools
adminautomation
Aibtc 308 tools
adminautomation
SmartBear MCP 243 tools
adminautomation
Google Super 200 tools
adminautomation
Arcane 180 tools
adminautomation
Propresenter 177 tools
adminautomation
Leaper Vision Toolkit 169 tools
adminautomation
Opencut Controller 161 tools
adminautomation

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

GET STARTED →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.