Query user names from VAST cluster using users/names endpoint
AI agents call query_users_vast to retrieve information from VAST Admin MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user information from a VAST cluster without creating, modifying, deleting, or executing any operations. It is a read-only query that returns existing data. The severity is low because user name enumeration poses minimal direct risk compared to tools that modify infrastructure or data.
From the tool's definition Tool name includes 'query', description states 'Query user names from VAST cluster', and the endpoint accessed ('users/names') is a straightforward data retrieval operation with no modification or execution capabilities.
Documented attack patterns abuse exactly the kind of access query_users_vast gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and VAST Admin MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for query_users_vast:
{
"version": "1",
"default": "deny",
"tools": {
"query_users_vast": {}
}
} query_users_vast 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 user names from VAST cluster using users/names endpoint. It is categorised as a Read tool in the VAST Admin MCP Server MCP Server, which means it retrieves data without modifying state.
Register the VAST Admin MCP Server MCP server in PolicyLayer and add a rule for query_users_vast: 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 VAST Admin MCP Server. Nothing to install.
query_users_vast 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_users_vast 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_users_vast. 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_users_vast is provided by the VAST Admin MCP Server MCP server (vast-data/vast-admin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from VAST Admin MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
16 VAST Admin MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.