search_milvus_collection
AI agents call search_milvus_collection 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.
The tool appears designed to query/retrieve data from a Milvus collection without creating, modifying, or deleting data. Search operations are typically read-only. Tool description is empty, which slightly lowers confidence, but the naming convention and server context strongly suggest a data retrieval operation with no side effects.
From the tool's definition Tool name 'search_milvus_collection' indicates a search operation on a Milvus vector database. Sibling tools on the server (get_github_repos, get_github_user_info, list_milvus_collections) are all read-only retrieval operations, establishing a pattern.
Attacks that exploit this kind of access
search_milvus_collection. 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 search_milvus_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 MCP Server. Nothing to install.
search_milvus_collection 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 search_milvus_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 search_milvus_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.
search_milvus_collection 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 →