Read vault items for context, and change credentials as an approved step
Connect 1Password and Luumen can look up the credential behind a runbook step without you switching windows. It lists vaults, lists items, and reads a specific item with its fields. When a secret needs to change after a rotation, Luumen writes the new value back to the same item and shows you the change first. Authentication is by API key.
6 tools: 3 read, 3 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed 1Password run looks like inside Luumen.
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as create item, delete item, update item. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to 1Password — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Connect in minutes. Every action scoped, approved, and audited from day one.