Fluxix Use Cases
Common kinds of agents and the Fluxix rule you would write for each. Thresholds are examples.
Payments & refund agents
Refunds above a threshold (for example args.amount > 100) require approval in the Fluxix dashboard. Card numbers are tokenized before reaching the model.
Database & SQL agents
DROP, DELETE FROM, TRUNCATE and ALTER TABLE statements are blocked, and the agent is told why so it can rewrite the query.
Customer support agents
Emails, phone numbers and card numbers are replaced with tokens such as [EMAIL_1] before reaching the model, and restored in the reply.
Email & outreach agents
Sends to more than a set number of recipients (for example 50) are held for approval.
DevOps & coding agents
Reads of system paths and .env files are blocked, and API keys and secrets are redacted from model traffic.