AI agents call query_cluster_metrics to retrieve information from Zilliz MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'query_cluster_metrics' tool appears to retrieve cluster performance metrics or monitoring data from a Milvus cluster. This is a read-only operation that queries existing metrics without modifying, deleting, or executing arbitrary operations. The empty description lowers confidence slightly, but the naming convention and context within a vector database server strongly suggests this is a Read operation.
From the tool's definition Tool name 'query_cluster_metrics' indicates a metrics querying operation. The server description emphasizes management operations like create, delete, insert, and search, but this tool's name suggests retrieval of monitoring/observability data without…
Documented attack patterns abuse exactly the kind of access query_cluster_metrics gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Zilliz MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for query_cluster_metrics:
{
"version": "1",
"default": "deny",
"tools": {
"query_cluster_metrics": {}
}
}query_cluster_metrics 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.
query_cluster_metrics. It is categorised as a Read tool in the Zilliz MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Zilliz MCP Server MCP server in PolicyLayer and add a rule for query_cluster_metrics: 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 Zilliz MCP Server. Nothing to install.
query_cluster_metrics 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 query_cluster_metrics 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 query_cluster_metrics. 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.
query_cluster_metrics is provided by the Zilliz MCP Server MCP server (zilliztech/zilliz-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 Zilliz MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
16 Zilliz MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.