List secrets at the specified path in Vault
AI agents call vault_list to retrieve information from Vault MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list' operation retrieves information about secrets stored at a path but does not read secret values, modify data, or trigger destructive actions. This is a read-only query operation with minimal blast radius—an attacker listing secrets could discover what secrets exist but cannot access their contents or cause harm without using companion tools like vault_read, vault_write, or vault_delete.
From the tool's definition Tool name 'vault_list' and description 'List secrets at the specified path in Vault' indicate querying/retrieving secret metadata without modification or deletion.
Attacks that exploit this kind of access
List secrets at the specified path in Vault. It is categorised as a Read tool in the Vault MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Vault MCP Server MCP server in PolicyLayer and add a rule for vault_list: 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 Vault MCP Server. Nothing to install.
vault_list 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 vault_list 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 vault_list. 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.
vault_list is provided by the Vault MCP Server MCP server (kelleyblackmore/vault-mcp). 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 →