List available 1Password vaults before configuring the provider. For service-account auth, pass the service account token directly.
AI agents call listVaults to retrieve information from Executor without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns a list of available vaults from 1Password. It performs a read-only operation to enumerate resources for configuration purposes. No data is created, modified, deleted, or financial operations are performed. While it does require authentication credentials (service account token), the action itself is purely informational retrieval.
From the tool's definition Tool name 'listVaults' and description explicitly states 'List available 1Password vaults' — a retrieval operation with no modification or deletion.
Documented attack patterns abuse exactly the kind of access listVaults gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Executor, and nothing reaches the server without passing your rules. This is the rule we recommend for listVaults:
{
"version": "1",
"default": "deny",
"tools": {
"listVaults": {}
}
}listVaults 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.
List available 1Password vaults before configuring the provider. For service-account auth, pass the service account token directly. It is categorised as a Read tool in the Executor MCP Server, which means it retrieves data without modifying state.
Register the Executor MCP server in PolicyLayer and add a rule for listVaults: 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 Executor. Nothing to install.
listVaults 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 listVaults 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 listVaults. 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.
listVaults is provided by the Executor MCP server (rhyssullivan/executor). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 29 Executor tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
29 Executor tools catalogued and risk-classified — across an index of 42,500+ MCP servers.