Agent inventory
Keep every AI agent and its access in view
An agent list is useful only when it explains the workflow around each entry. Roxea connects ownership and purpose to the tools and permissions that create real exposure.
The problem: agent records are scattered
One team keeps an n8n workflow list. Another has a document of internal assistants. A consultant holds the client context in a delivery spreadsheet. Nobody has the full view.
When a security or leadership question arrives, teams spend the review rebuilding scope instead of assessing it.
How agent inventory works in Roxea
Create an agent record with its purpose, department, owner, status and autonomy. Add every external tool, then describe the access and safeguards for that specific connection.
- Keep ownership and business context next to technical access.
- Distinguish read, write, send and high-impact capabilities.
- Record human approval, logs and kill switches.
- Link current findings, actions and review history.
- Filter and review agents by risk level or department.
Example: a support refund agent
The inventory shows that the agent reads support tickets, drafts replies and requests Stripe refunds. It also shows whether refund submission needs approval, who owns the workflow and when permissions were last reviewed.
A reviewer can understand the operating boundary without reading the automation itself.
FAQ
Questions people ask before a review
Continue the review
Related guides and product details
Build the inventory before the next access review.
Start with one agent and record the tools, permissions and people around it.