Drive a real browser for the checks no API exposes
Some things only exist in a web UI: a vendor status page, a legacy admin console, a login flow that has to be clicked through. Browser Tool lets Luumen run an automated browser session against those pages, watch the run as it happens, and pull back whatever it captured. No credential to configure. Running a task is an approved step.
5 tools: 3 read, 2 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Browser Tool run looks like inside Luumen.
Browser Tool needs no credential of its own, so there is nothing to authorize. Access is still granted per agent, skill, and team inside Luumen, and every call is logged.
This connection exposes write actions such as run browser task, stop browser task. 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 Browser Tool — 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.