Load a collection into memory for search and query. Args: collection_name: Name of collection to load replica_number: Number of replicas
AI agents invoke milvus_load_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.
This tool triggers an external operation on the Milvus database — loading a collection into memory. It doesn't merely read data, nor does it write/modify data or delete anything. It executes a state-changing operation on the database system (memory allocation, replica provisioning) whose effects depend on the arguments provided.
From the tool's definition Load a collection into memory for search and query
Documented attack patterns abuse exactly the kind of access milvus_load_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_load_collection:
{
"version": "1",
"default": "deny",
"tools": {
"milvus_load_collection": {
"limits": [
{
"counter": "milvus_load_collection_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}milvus_load_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.
Free to start. No card required.
Load a collection into memory for search and query. Args: collection_name: Name of collection to load replica_number: Number of replicas. 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.
Register the MCP Server for Milvus MCP server in PolicyLayer and add a rule for milvus_load_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.
milvus_load_collection is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the milvus_load_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.
Set action: deny in the PolicyLayer policy for milvus_load_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.
milvus_load_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.
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.