Read index state and namespace counts, then take backups with approval
Connect Pinecone and Luumen can read your index configuration, per-namespace vector counts, index fullness, backup details, and the status of bulk imports and restore jobs. When something needs to change — a new index, a backup before a reindex, a namespace, a bulk import from object storage — the agent shows the plan first and asks. Auth is by API key.
47 tools: 27 read, 20 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Pinecone 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.
Read actions answer immediately. Anything that writes — cancel bulk import, configure index, create assistant, create backup, and more — is shown as a plan and requires approval by default, including the 7 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
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 Pinecone — 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.