AI agents use milvus_create_collection to create or update resources in MCP Server for Milvus — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Server for Milvus environment.
This tool creates a new collection in Milvus, which is a Write operation—it modifies database state by introducing a new collection. This is reversible (collections can be deleted), so it does not rise to Destructive. The impact is limited to schema creation without data deletion, making it Write rather than Execute.
From the tool's definition Tool named 'milvus_create_collection' on a Milvus vector database server. 'Create' operations add new data structures (collections) to the database.
Documented attack patterns abuse exactly the kind of access milvus_create_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_create_collection:
{
"version": "1",
"default": "deny",
"tools": {
"milvus_create_collection": {
"limits": [
{
"counter": "milvus_create_collection_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}milvus_create_collection stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
milvus_create_collection. It is categorised as a Write tool in the MCP Server for Milvus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Server for Milvus MCP server in PolicyLayer and add a rule for milvus_create_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_create_collection is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the milvus_create_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_create_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_create_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.