vault_list

List your vault entries — names, kind, metadata, timestamps ONLY (never values). Requires your secret (Bearer).

SERVERGateway SOURCEhttps://wingmanprotocol.com/mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-wingmanprotocol-agent-gateway/vault-list.md

WHAT IT DOES

What vault_list does on Gateway

AI agents call vault_list to retrieve information from Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`handle`	string	Yes	your registered handle

Parameters from the server's own tool schema.

RISK

Why vault_list is rated Low

This is a read-only operation that queries a vault to retrieve metadata about stored entries. The restriction against returning values means no sensitive secrets are exposed by the tool itself. While it requires authentication (Bearer token), it performs no modifications, executions, or destructive actions.

From the tool's definition Tool description explicitly states it lists vault entries with "names, kind, metadata, timestamps ONLY (never values)". The phrase "ONLY (never values)" confirms this retrieves metadata without exposing sensitive data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs vault_list safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vault_list, this is the rule to start with:

vault_list Allowed

vault_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "vault_list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every vault_list call is checked against it from then on.

FAQ

Questions about vault_list

What does the vault_list tool do? +

List your vault entries — names, kind, metadata, timestamps ONLY (never values). Requires your secret (Bearer). It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.

What parameters does vault_list accept? +

vault_list accepts 1 parameter: handle. Required: handle. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on vault_list? +

Register the Gateway 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 Gateway. Nothing to install.

What risk level is vault_list? +

vault_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit vault_list? +

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.

How do I block vault_list completely? +

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.

What MCP server provides vault_list? +

vault_list is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Gateway, and thousands of servers like it.

This server

All 271 Gateway tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →