AI agents call list_projects 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 'list_' prefix is a strong indicator of a read-only query operation. Given the Zilliz server context where other tools handle creation (create_collection, create_free_cluster), deletion (delete_entities), and search (hybrid_search), 'list_projects' clearly performs data retrieval. No destructive, modifying, or executable actions are implied. The empty description lowers confidence slightly from 0.9 to 0.85.
From the tool's definition Tool name 'list_projects' indicates a retrieval operation with no modification. The description is empty, but the naming convention and context of a Zilliz MCP server (which manages clusters and collections) suggests this lists existing projects/resources…
Documented attack patterns abuse exactly the kind of access list_projects 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_projects:
{
"version": "1",
"default": "deny",
"tools": {
"list_projects": {}
}
}list_projects 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_projects. 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_projects: 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_projects 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_projects 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_projects. 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_projects 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.