Critical Risk →

delete-tasks

Delete completed tasks

How to control delete-tasks ↓

What delete-tasks does on Meilisearch MCP Server

AI agents call delete-tasks to permanently remove resources in Meilisearch MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete-tasks needs a policy

Deletion operations are irreversible and cannot be undone without external backups or recovery mechanisms. Even though the tool is scoped to 'completed' tasks, the destructive nature of permanent removal makes this Destructive rather than Write.

From the tool's definition Tool name is 'delete-tasks' with description 'Delete completed tasks'. The verb 'delete' and the action of removing tasks from the Meilisearch system indicates irreversible data removal.

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

How to control delete-tasks

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-tasks:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete-tasks"
  ]
}

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

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete-tasks

What does the delete-tasks tool do? +

Delete completed tasks. 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-tasks? +

Register the Meilisearch MCP Server MCP server in PolicyLayer and add a rule for delete-tasks: 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-tasks? +

delete-tasks 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-tasks? +

Yes. Add a rate_limit block to the delete-tasks 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-tasks completely? +

Set action: deny in the PolicyLayer policy for delete-tasks. 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-tasks? +

delete-tasks 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.

Free to start. No card required.

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

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.