Peaka
for LuumenAI
Query Peaka projects, browse catalogs, and change workspaces with approval
Connect Peaka and your agent can walk the organization, workspace, and project hierarchy, browse catalogs, schemas, tables, and columns, and run read-only SQL against a project to answer a question directly. Changes to the hierarchy — new workspaces and projects, renames, deletions — are previewed and sent for approval first. Luumen authenticates with an API key.
The Peaka toolbox
9 tools: 3 read, 6 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadExecute QueryExecute one read-only SQL SELECT or CTE ending in LIMIT 1-1000 in a Peaka project and return rows in SIMPLE object format.
- ReadList Data ResourcesBrowse a project's catalogs, schemas, tables, or columns to discover qualified resources for SQL queries.
- ReadList HierarchyList organizations, workspaces in an organization, or projects in a workspace, returning the IDs needed for hierarchy administration.
- WriteCreate ProjectCreate a project in a Peaka workspace and return its project ID and available project details for use with Peaka data and query tools. Approval by default
- WriteCreate WorkspaceCreate a workspace in an organization and return its workspace ID and details. Approval by default
- WriteDelete ProjectPermanently delete a project and its project-scoped data from a Peaka workspace. Approval by default
- WriteDelete WorkspacePermanently delete a workspace. Approval by default
- WriteUpdate ProjectReplace the name and optional description of a project in its current workspace. Approval by default
- WriteUpdate WorkspaceReplace the name and optional description of an existing workspace. Approval by default
One prompt, start to finish
What a governed Peaka run looks like inside Luumen.
Questions
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 — create project, create workspace, delete project, delete workspace, and more — is shown as a plan and requires approval by default, including the 2 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 Peaka — 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.
Often connected alongside
All integrations
PostgreSQLQuery PostgreSQL state safely; maintenance held for approval.
MySQLQuery MySQL state safely; maintenance held for approval.
Microsoft SQL ServerQuery Microsoft SQL Server state safely; maintenance held for approval.Oracle DatabaseQuery Oracle Database state safely; maintenance held for approval.Put Peaka to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.