AI agents call delete-key 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.
Deleting an API key is a destructive action—once removed, the key is permanently lost and cannot be recovered through normal means. This is more severe than a Write operation (which is reversible) because deletion is irreversible. While not as critical as financial impact, a deleted API key could break integrations and access controls, making this a high-severity destructive action.
From the tool's definition Tool name is 'delete-key' with description 'Delete an existing API key'. The verb 'delete' and the action of removing an API key are irreversible operations that cannot be undone.
Documented attack patterns abuse exactly the kind of access delete-key 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 delete-key:
{
"version": "1",
"default": "deny",
"hide": [
"delete-key"
]
} delete-key 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.
Delete an existing API key. 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 delete-key: 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.
delete-key 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 delete-key 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 delete-key. 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.
delete-key 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.