Inspect Metatext AI guardrails, then change them as an approved step
Connect Metatext AI and the agent can read your applications, models, and guardrail policies while you work. Ask what a policy covers today, classify or extract from sample text, or check which red team probes exist. When a policy needs to change, the agent shows the edit first and waits for your approval before sending it. Authentication is by API key.
13 tools: 9 read, 4 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Metatextai 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 — create policy guardrails, delete guardrail policy, run red team test scan, update policy guardrails — is shown as a plan and requires approval by default, including the 1 action 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 Metatextai — 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.