Agent Control
Before an agent sends information, approves a payment or changes a system, Gluon checks the action: allowed, blocked or approval required.
- AllowedQueue an invoice of EUR 1,200 for payment
- Approval requiredApprove an invoice of EUR 40,000
- BlockedChange a supplier’s bank account number
How it works
Define the action.
Actions are defined in the model with their effects, approvers and risk tier. A new tool starts switched off.
Paying too much
A finance agent processes supplier invoices. It is useful for the hundreds of small ones, but the procurement procedure says a second approver signs above EUR 10,000, and only the supplier team may change bank details after a call-back check. An email asking for a new account number looks like any other request.

Questions
Who decides which actions need approval?
Your rules do. Actions are defined in the model with their effects, approvers and risk tier, and the kill switch stops any action at once, without a new version.
Can we stop an action at once?
Yes. The kill switch stops any action, source or model at once, without publishing a new version, and the reason is audited.
Does Gluon run long processes itself?
No. Gluon decides and executes single actions. Long-running processes belong to the agent platform you use, which receives an approved action.
Get started
You bring one question your team has to get right. The people who build Gluon sit down with you and build it together, in your own environment.

- Choose one question and its outcome.
With the people who build Gluon, you pick one question that must be right, with an owner and a clear outcome.
- Set the boundary and connect the sources.
Name the sources, their owners and what must never be returned. Gluon connects them in your own environment, with the permissions they already have.
- Test it with your people.
Your people ask real questions, including conflicting versions and requests outside their scope. Their questions and corrections show what to refine.
- Decide and go live.
Business, security and operations judge the result against the outcome you set. Then the use case runs where your people work.