Switch to a different database. Args: db_name: Name of the database to use
AI agents call milvus_use_database to retrieve information from MCP Server for Milvus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Even though milvus_use_database only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Documented attack patterns abuse exactly the kind of access milvus_use_database 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_use_database:
{
"version": "1",
"default": "deny",
"tools": {
"milvus_use_database": {}
}
}milvus_use_database is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Switch to a different database. Args: db_name: Name of the database to use. It is categorised as a Read tool in the MCP Server for Milvus MCP Server, which means it retrieves data without modifying state.
Register the MCP Server for Milvus MCP server in PolicyLayer and add a rule for milvus_use_database: 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_use_database is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the milvus_use_database 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_use_database. 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_use_database 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.