Get all NDB users. Filtering is done using valueType and value fields, which are used to filter the response sent by the NDB API, for flexible filtering. You can filter by any of the following attribute names available in the user object: - username: user login, string - email: user email, string...
AI agents call list_users 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 performs a query operation that retrieves and lists existing user data from the Nutanix Database Service without any side effects, modifications, or irreversible actions. It is purely informational/read-only. The severity is low because exposing a list of users in a database management system poses minimal risk compared to tools that can provision, delete, or execute operations.
From the tool's definition Tool description states 'Get all NDB users' with filtering capabilities. The tool retrieves user information (username, email, isExternalAuth, passwordExpired) without modification, creation, deletion, or execution of operations.
Attacks that exploit this kind of access
Get all NDB users. Filtering is done using valueType and value fields, which are used to filter the response sent by the NDB API, for flexible filtering. You can filter by any of the following attribute names available in the user object: - username: user login, string - email: user email, string - isExternalAuth: true if user is authenticated on an external directory (Active Directory), boolean - passwordExpired: true if password is expired, boolean Examples: - To filter by username: valueType =. 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_users: 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_users 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_users 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_users. 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_users 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 →