AI agents use create_collection to create or update resources in Zilliz MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zilliz MCP Server environment.
Creating a collection is a write operation that initializes new database schema/structure. While reversible (collections can be deleted), it modifies the database state and could impact system configuration if misused by an agent.
From the tool's definition Tool name 'create_collection' indicates creation of a data structure within a Milvus vector database. Server description confirms the server 'allows users to...manage collections.' Collection creation is a reversible write operation typical of database schema…
Documented attack patterns abuse exactly the kind of access create_collection gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Zilliz MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_collection:
{
"version": "1",
"default": "deny",
"tools": {
"create_collection": {
"limits": [
{
"counter": "create_collection_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
create_collection. It is categorised as a Write tool in the Zilliz MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Zilliz MCP Server MCP server in PolicyLayer and add a rule for 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 Zilliz MCP Server. Nothing to install.
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 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 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.
create_collection is provided by the Zilliz MCP Server MCP server (zilliztech/zilliz-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 Zilliz MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
16 Zilliz MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.