List all collections in the Milvus database.
AI agents call list_milvus_collections to retrieve information from MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns metadata about existing Milvus collections without modifying, creating, or deleting any data. It is a read-only operation with minimal blast radius—the worst outcome is information disclosure about the database structure. No side effects, no data modification, no execution of arbitrary code.
From the tool's definition Tool name 'list_milvus_collections' and description 'List all collections in the Milvus database' indicate a retrieval operation with no modification or deletion capability.
Attacks that exploit this kind of access
List all collections in the Milvus database. It is categorised as a Read tool in the MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Server MCP server in PolicyLayer and add a rule for list_milvus_collections: 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. Nothing to install.
list_milvus_collections 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 list_milvus_collections 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 list_milvus_collections. 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.
list_milvus_collections is provided by the MCP Server MCP server (namto908/mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →