Read log volume and alert config in Mezmo, then change it as an approved step
Connect Mezmo and Luumen can read your ingestion status, views, preset alerts, exclusion rules, API keys, and team membership without leaving the terminal. Ask why ingest spiked last night, then act on the answer. Changes like adding an exclusion rule or inviting a member are previewed and approved before they run. Authentication is by API key.
36 tools: 14 read, 22 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Mezmo 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 category, create ingestion exclusion rule, create api key, create member invitation, and more. 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 Mezmo — 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.