[ SOX / Inventory ]

Know which agents touch the ledger

Auditors and COSO’s new guidance both start with the same question: which AI is in use, who owns it, and what can it reach? When agents reach your financial systems through engini, you can answer from one place: every MCP server and toolset, the connections and tools each one exposes, who connects, and a record of every run.

ITGC: accessCOSO GenAI guidanceNetSuiteSAP S/4HANASalesforce
Read about engini skills →
A quarterly inventory
  1. Quarter endschedule trigger
  2. List MCP servers and toolsetsengini REST API
  3. Tools and connections each exposeswhich systems, which accounts
  4. Who connectsusers of each MCP server
  5. Inventory for reviewowner sign-off in your process
Illustration of the flow on this page, not a product screen.
What it is
A current inventory of agent access to financial systems
Control area
COSO GenAI inventory; ITGC access to programs and data
engini provides
MCP servers, toolsets and connections listable by API; who connects; run records
You still own
Owners, sign-off, and agents that do not go through engini
[ 01 / The problem ]

You cannot control what you cannot list

Blurred landscape photo with the words Agent inventory and the labels Route, List, Attribute, Review

COSO’s February 2026 guidance on generative AI begins with governance and an inventory of AI use, including shadow AI, with clear ownership (Journal of Accountancy). KPMG lists a central agent inventory with owners among its design considerations for agentic workflows in financial reporting (KPMG, 2026). EY’s 2026 survey found that a quarter of companies using agents cannot detect unauthorized agents internally (EY).

What the inventory has to answer

  • Which agents and assistants reach financial systems.
  • Which tools each one can call, on which accounts.
  • Who uses each one, and who owns it.
  • What each one did in the period.

How engini helps

When agent access to NetSuite, SAP, Salesforce and your other systems goes through engini, the access is defined in engini: MCP servers limited to the connections and tools chosen for them, and toolsets for SDK, CLI and REST API calls. engini’s REST API lists MCP servers, the tools each exposes and the toolsets, engini shows who uses each MCP server, and every run is recorded under the user who triggered it. A scheduled workflow can turn that into an inventory sheet each quarter for owners to review.

The limit matters: engini does not discover agents that do not connect through engini. The inventory is complete only if your policy routes agent access to financial systems through engini; where a company allows no MCP access except engini’s, the view covers every employee using AI that way.

[ 02 / How it works ]

An inventory your auditor can follow

engini provides the list. Ownership and sign-off stay in your process.

01 / Route

Agents go through engini

Set the policy that agent access to financial systems goes through engini MCP servers and toolsets.

02 / List

Pull the inventory

A scheduled workflow lists MCP servers, the tools and connections each exposes, and toolsets, through the engini REST API.

03 / Attribute

Who uses what

engini shows who uses each MCP server, and the audit log records every run under the user who triggered it.

04 / Review

Owners sign off

The inventory goes to a sheet each quarter; each owner confirms their agents in your review process.

This is the flow you will build. Start free and connect your systems.

[ 03 / What the agent reads and writes ]

Where the inventory comes from

SystemRecordsAccess
enginiMCP servers and the tools and connections each exposes (REST API)Read
enginiToolsets for SDK, CLI and REST API agentsRead
enginiWho uses each MCP server; History and audit logRead
Excel or Google SheetsThe quarterly inventory for owner reviewWrite

Connect these systems in engini and give the agent only these tools.

[ 04 / Build it with the engini skill ]

Describe it in plain words. The engini skill builds the workflow.

engini skills is engini’s plugin for Claude Code and Codex. Its workflow agent, Flo, turns a plain-language request into an engini workflow: it designs the steps, dry-runs them against your own engini account, shows you a proposal, and creates the workflow only after you approve it, always turned off. You check it in the engini designer and turn it on.

Blurred landscape photo with the word inventory and the labels MCP servers, toolsets, who connects

Editorial image: every agent, listed.

Claude Code: install once
/plugin marketplace add engini/skills
/plugin install skills@engini
Then ask for this solution
Build a workflow in my engini account: on the last day of each quarter, list all my engini MCP servers with the connections and tools each one exposes, and all toolsets, and write them as rows to a new tab in the "AI agent inventory" Google Sheet with an empty Owner column.
  1. You need an engini account, the engini CLI (npm i -g @engini/cli) and a workspace-scoped API key, ideally a dedicated least-privilege one.
  2. Connect the systems this flow uses in engini first. Flo never creates or changes a connection and never handles your key; it tells you which command to run.
  3. Flo checks your login and workspace, searches the tool catalog, compiles the plan and shows a proposal table with every step. It creates the workflow only when you approve that proposal, and it creates it turned off.
  4. Open it in the engini designer, fill anything it left for you, and turn it on.
engini skills for Claude Code and Codex →
What the skill will never do on its own →
[ 05 / Agent Policy ]

What the inventory covers, and what it cannot

Listed

Everything defined in engini

MCP servers, the connections and tools each one exposes, and toolsets, all listable through the engini REST API.

Attributed

Who connects and what ran

engini shows who uses each MCP server and records every run under the user who triggered it.

Recorded

Exportable evidence

The audit log supports export and SIEM streaming, so the inventory and the activity behind it can be kept with your audit evidence.

Not covered

Agents outside engini

engini does not discover agents that do not connect through engini. It has no approval step, no SCIM and no SOC 1 report.

SOC 2 Type IIISO 27001GDPRHIPAA compliant
[ 06 / Try it now ]

Build it on your own data today

Start free, connect your systems, and build this flow with the engini skill, in Workflow Studio, or from your own agent.

  • 01Workflow Studio. Build the flow on a visual canvas, with an AI agent step where judgment is needed. Start free →
  • 02Your own agent. Give Claude, ChatGPT or Cursor an engini MCP server with only these tools. MCP client setup →
  • 03The engini skill. Ask Flo in Claude Code or Codex and review its proposal. Install the skill →
[ 07 / Questions ]

Questions buyers ask before they start

Can engini give us an inventory of AI agents?

Of the agent access that goes through engini, yes: MCP servers, the tools and connections each exposes, toolsets, who connects and what ran. engini does not discover agents that do not connect through engini.

How do we make the inventory complete?

Route agent access to financial systems through engini by policy. Where a company allows no MCP access except engini’s, engini’s view covers every employee using AI that way.

Can the inventory be produced automatically?

Yes. engini’s REST API lists MCP servers and toolsets, so a scheduled workflow can write the inventory to a sheet each quarter for owners to review.

Who owns each agent?

You decide. engini records who created each toolset and who uses each MCP server; ownership and sign-off stay in your review process.