Add a dynamic field to an existing collection
AI agents use milvus-create-dynamic-field to create or update resources in Milvus MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Milvus MCP Server environment.
This tool creates/modifies database structure (adding a field to a collection) but does not delete data or execute arbitrary code. It is reversible (the field can be removed or the collection recreated). This qualifies as Write rather than Destructive.
From the tool's definition Tool description: 'Add a dynamic field to an existing collection' — this modifies the schema of an existing collection by adding a new field, which is a reversible structural change to the database.
Documented attack patterns abuse exactly the kind of access milvus-create-dynamic-field gives an agent:
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-create-dynamic-field:
{
"version": "1",
"default": "deny",
"tools": {
"milvus-create-dynamic-field": {
"limits": [
{
"counter": "milvus-create-dynamic-field_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} milvus-create-dynamic-field 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.
Add a dynamic field to an existing collection. It is categorised as a Write tool in the Milvus MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Milvus MCP Server MCP server in PolicyLayer and add a rule for milvus-create-dynamic-field: 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.
milvus-create-dynamic-field 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-dynamic-field 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-dynamic-field. 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-dynamic-field 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.
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.
Free to start. No card required.
21 Milvus MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.