1
[Feature request] Scoped, metadata-only API for AI agents managing collections/groups
Source: dani-garcia/vaultwarden#7593 · opened by @suantea
Motivation I'd like to let an AI agent help manage my vault organization (grouping collections, cleaning up structures, re-categorizing items). Today the only way to do this programmatically is the admin API, which is all-or-nothing: an agent with access to it can read/export everything. Security concern A vault server holds ciphertext (safe without the master password) but also *plaintext metadata* (item names, URLs, usernames, org/collection/group structure) that is itself sensitive. An agent integrating with a third-party LLM would ship this metadata off-box, and a broad admin token also turns prompt injection into a destructive capability (delete groups, change permissions, export). Proposal Add a scoped agent token / API surface with: 1. Fine-grained scopes (e.g. groups:read, groups:write, collections:read, collections:write) — never including ciphertext read or export. 2. Metadata-only endpoints that never return ciphertext fields, so agents only ever see names/IDs/st…
No pledges yet. Be the first to back this.
Comments
Similar requests
[duplicate] As my user has "manager" role on multiple collections, I want to invite a user to multiple collections at once
1 vote · 0 comments
Deleting a collection - Backend says Yes, Frontend says No. Can we fix that?
1 vote · 0 comments
Feature Request: Map OIDC group claims to Collections (post-authentication)
9 votes · 0 comments
[Feature Request] Option to collapse all collections by default across Web UI and apps
1 vote · 0 comments
Right to invite new users without accessing all collections
3 votes · 0 comments
No comments yet.