delete-index

THE RISK

Critical Risk

Why delete-index needs a policy

Deletion of an index and all its documents is a destructive operation that cannot be undone. This falls into the Destructive category per the classification rules. The severity is high because accidental or malicious use could result in significant data loss, though the blast radius depends on whether the index contains critical data (limited to a Meilisearch instance, not financial systems).

From the tool's definition Tool name is 'delete-index' and description explicitly states 'Delete an existing index and all its documents' — this irreversibly removes an entire index and all associated data.

Documented attack patterns abuse exactly the kind of access delete-index gives an agent:

POLICY

How to control delete-index

PolicyLayer is an MCP gateway — it sits between your AI agents and Meilisearch MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete-index:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete-index"
  ]
}

delete-index disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Meilisearch MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Meilisearch MCP Server tools

Destructive cancel-tasks Cancel pending or enqueued tasks Destructive delete-key Delete an existing API key Destructive delete-tasks Delete completed tasks Write add-documents Add or update documents in an index Write create-index Create a new index with optional primary key Write create-key Create new API key with specific permissions Write update-connection-settings Update URL and/or API key to connect to a different instance Write update-settings Update index settings (ranking, faceting, etc.)

All 23 Meilisearch MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Meilisearch MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete-index

What does the delete-index tool do? +

Delete an existing index and all its documents. It is categorised as a Destructive tool in the Meilisearch MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete-index? +

Register the Meilisearch MCP Server MCP server in PolicyLayer and add a rule for delete-index: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Meilisearch MCP Server. Nothing to install.

What risk level is delete-index? +

delete-index is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete-index? +

Yes. Add a rate_limit block to the delete-index rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block delete-index completely? +

Set action: deny in the PolicyLayer policy for delete-index. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides delete-index? +

delete-index is provided by the Meilisearch MCP Server MCP server (meilisearch/meilisearch-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Meilisearch MCP Server tool call.

Start from Meilisearch MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →