Perform hybrid search combining text and vector search. Args: collection_name: Name of collection to search query_text: Text query for BM25 search text_field: Field name for text search vector: Query vector for dense vector search vector_field: Field name for vector search limit: Maximum number o...
AI agents call milvus_hybrid_search 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.
This tool retrieves and queries data from a Milvus vector database using hybrid search capabilities (combining BM25 text search and dense vector search). The operation has no side effects—it only returns results based on search criteria. The filter expressions and range searches are query constraints, not data-modifying operations.
From the tool's definition Tool performs 'hybrid search combining text and vector search' with read-only parameters: collection_name, query_text, vector, limit, output_fields, and optional filters. No data modification, deletion, or execution of arbitrary code occurs.
Documented attack patterns abuse exactly the kind of access milvus_hybrid_search 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_hybrid_search:
{
"version": "1",
"default": "deny",
"tools": {
"milvus_hybrid_search": {}
}
}milvus_hybrid_search 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.
Perform hybrid search combining text and vector search. Args: collection_name: Name of collection to search query_text: Text query for BM25 search text_field: Field name for text search vector: Query vector for dense vector search vector_field: Field name for vector search limit: Maximum number of results output_fields: Fields to return in results filter_expr: Optional filter expression sparse_radius: Optional lower bound for sparse range search sparse_range_filter: Optional upper bound for sparse range search dense_radius: Optional lower bound for dense range search dense_range_filter: Optional upper bound for dense range search. 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_hybrid_search: 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_hybrid_search 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_hybrid_search 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_hybrid_search. 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_hybrid_search 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.