High Risk →

milvus_release_collection

Release a collection from memory. Args: collection_name: Name of collection to release

How to control milvus_release_collection ↓

AI agents invoke milvus_release_collection to trigger actions in MCP Server for Milvus. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

High Risk

Releasing a collection from memory is an operational action that affects the runtime state of the database system — it unloads the collection so it can no longer serve queries until reloaded. This is not a simple read, write, or delete of data, but an execution of a system-level operation that changes the availability state of the collection.

From the tool's definition Release a collection from memory

Documented attack patterns abuse exactly the kind of access milvus_release_collection gives an agent:

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "milvus_release_collection": {
      "limits": [
        {
          "counter": "milvus_release_collection_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

milvus_release_collection stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register MCP Server for Milvus — 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.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the milvus_release_collection tool do? +

Release a collection from memory. Args: collection_name: Name of collection to release. It is categorised as a Execute tool in the MCP Server for Milvus MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on milvus_release_collection? +

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

What risk level is milvus_release_collection? +

milvus_release_collection is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit milvus_release_collection? +

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

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

milvus_release_collection is provided by the MCP Server for Milvus MCP server (zilliztech/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 MCP Server for Milvus tool call.

Deterministic rules across all 14 MCP Server for Milvus tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

14 MCP Server for Milvus tools catalogued and risk-classified — across an index of 42,500+ 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.