Low Risk

vault_list

List all 1Password vaults accessible to the service account. Returns vault IDs, names, descriptions, and types.

Part of the 1password MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call vault_list to retrieve information from 1password without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though vault_list only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

io-github-cakerepository-1password.yaml
tools:
  vault_list:
    rules:
      - action: allow

See the full 1password policy for all 8 tools.

Tool Name vault_list
Category Read
Risk Level Low

Agents calling read-class tools like vault_list have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the vault_list tool do? +

List all 1Password vaults accessible to the service account. Returns vault IDs, names, descriptions, and types.. It is categorised as a Read tool in the 1password MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on vault_list? +

Add a rule in your Intercept YAML policy under the tools section for vault_list. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the 1password MCP server.

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 Intercept 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 Intercept 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 1password MCP server (@takescake/1password-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on 1password

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.