List all workspace vaults
AI agents call list_workspace_vaults to retrieve information from Dust 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 and enumerates workspace vaults without creating, modifying, deleting, executing, or moving resources. It is purely informational. While it may expose organizational data structure, there are no irreversible consequences or external effects from calling it. Severity is low because listing vaults is a fundamental query operation with minimal blast radius.
From the tool's definition Tool name 'list_workspace_vaults' with description 'List all workspace vaults' indicates a retrieval/query operation with no side effects. The verb 'list' is a clear indicator of a Read operation that returns information without modification.
Attacks that exploit this kind of access
List all workspace vaults. It is categorised as a Read tool in the Dust MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Dust MCP Server MCP server in PolicyLayer and add a rule for list_workspace_vaults: 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 Dust MCP Server. Nothing to install.
list_workspace_vaults 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_workspace_vaults 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_workspace_vaults. 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_workspace_vaults is provided by the Dust MCP Server MCP server (ma3u/dust-mcp-server-postman-railway). 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 →