AI agents call cancel-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.
Cancelling tasks is an irreversible action — once a task is cancelled, it cannot be re-queued or restarted automatically. This permanently stops pending operations (such as indexing jobs, document additions, etc.), which could result in data loss or incomplete state. The irreversible nature places this in the Destructive category, with high severity given it could affect many queued operations at once.
From the tool's definition Cancel pending or enqueued tasks
Documented attack patterns abuse exactly the kind of access cancel-tasks gives an agent:
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 cancel-tasks:
{
"version": "1",
"default": "deny",
"hide": [
"cancel-tasks"
]
}cancel-tasks disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Cancel pending or enqueued 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.
Register the Meilisearch MCP Server MCP server in PolicyLayer and add a rule for cancel-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.
cancel-tasks is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cancel-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.
Set action: deny in the PolicyLayer policy for cancel-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.
cancel-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.
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.