AI agents call list_clusters 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.
Despite the empty description, the tool name 'list_clusters' clearly indicates a retrieval operation that queries and returns cluster information without modifying state. Consistent with standard database/cloud API patterns, 'list' operations are read-only queries. Confidence is high based on the naming convention, though the empty description prevents absolute certainty (hence not 0.95+).
From the tool's definition Tool name 'list_clusters' combined with sibling tools that include create/delete/insert operations indicates this performs a listing/query operation.
Documented attack patterns abuse exactly the kind of access list_clusters 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 list_clusters:
{
"version": "1",
"default": "deny",
"tools": {
"list_clusters": {}
}
}list_clusters 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.
list_clusters. 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 list_clusters: 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.
list_clusters 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_clusters 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_clusters. 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_clusters 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.