milvus-delete-entities

THE RISK

Critical Risk

Why milvus-delete-entities needs a policy

This tool permanently removes data from the Milvus vector database collection. Deletion is an irreversible operation that cannot be undone. While the filter expression provides some guardrail against accidental deletion of entire collections, a malicious or careless AI agent could still cause significant data loss by crafting a broad filter or deleting critical entities.

From the tool's definition Tool name contains 'delete' and description states 'Delete entities from a collection based on filter expression'. The delete operation on database entities is irreversible.

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

POLICY

How to control milvus-delete-entities

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

policy.json

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

milvus-delete-entities 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 Milvus 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 Milvus MCP Server tools

Execute milvus-load-collection Load a collection into memory for search and query Execute milvus-release-collection Release a collection from memory Write milvus-bulk-insert Insert data in batches for better performance Write milvus-create-collection Create a new collection with specified schema Write milvus-create-dynamic-field Add a dynamic field to an existing collection Write milvus-create-index Create an index on a vector field Write milvus-insert-data Insert data into a collection Write milvus-upsert-data Upsert data into a collection (insert or update if exists)

All 21 Milvus 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 Milvus 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 milvus-delete-entities

What does the milvus-delete-entities tool do? +

Delete entities from a collection based on filter expression. It is categorised as a Destructive tool in the Milvus 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 milvus-delete-entities? +

Register the Milvus MCP Server MCP server in PolicyLayer and add a rule for milvus-delete-entities: 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 Milvus MCP Server. Nothing to install.

What risk level is milvus-delete-entities? +

milvus-delete-entities 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 milvus-delete-entities? +

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

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

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

Enforce policy on every Milvus MCP Server tool call.

Start from Milvus 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 →