Get list of all Nutanix clusters with advanced filtering and reduced schema mapping. Returns only the most relevant fields for each cluster. Returned fields: - id: string - name: string - uniqueName: string - ipAddresses: string[] - fqdns: string[] - description: string - cloudType: string - date...
AI agents call list_clusters to retrieve information from NDB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves cluster information without side effects. It performs a simple enumeration/listing operation that does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal—an agent could enumerate clusters but cannot provision, clone, delete, or trigger any management operations. This is a standard Read operation on infrastructure metadata.
From the tool's definition Tool name 'list_clusters' and description 'Get list of all Nutanix clusters' indicate retrieval of cluster metadata. Returns only informational fields (id, name, status, version, etc.) with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get list of all Nutanix clusters with advanced filtering and reduced schema mapping. Returns only the most relevant fields for each cluster. Returned fields: - id: string - name: string - uniqueName: string - ipAddresses: string[] - fqdns: string[] - description: string - cloudType: string - dateCreated: string - dateModified: string - ownerId: string - status: string - version: string - hypervisorType: string - hypervisorVersion: string Advanced Filtering: - Use valueType/value to filter the result set after mapping. Supports all returned fields, including array length (e.g. ipAddresses, fqdns). - Operators: !value (not), >value/<value (comparison), *value* (contains) - Multiple filters: combine with comma-separated valueType/value pairs - Examples: - Find clusters with name containing. It is categorised as a Read tool in the NDB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the NDB 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 NDB 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 NDB MCP Server MCP server (rouxton/ndb-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 →