Skip to main content
Connect your AI

StackJack's own AI use in AI Governance

AI Governance also records AI use that happens inside StackJack. There are two sources for it: StackJack MCP tool calls and StackJack automation runs. StackJack creates them. You do not add them. This…

Written By Christopher Scaminaci

Last updated 13 days ago

AI Governance also records AI use that happens inside StackJack. There are two sources for it: StackJack MCP tool calls and StackJack automation runs. StackJack creates them. You do not add them. This page says what each records and what each never records.

At a glance

  • What it does: shows your automations and the tool calls through StackJack next to the rest of your AI use.
  • Plan: every plan for the automation run facts. Scanning the tool calls follows your plan. See Data-loss rules, findings and scanning StackJack tool traffic.
  • Who: an Administrator can see the sources. You cannot add one or raise its capture level.
  • Where: AI Governance → Connected accounts → All sources, and the facts in Activity → Activity explorer.

StackJack automation runs

When one of your automations finishes a run, AI Governance records one fact for it. The fact shows:

  • how the run ended,
  • when it started and finished,
  • how many tool calls the run made,
  • the model it used.

If the run used StackJack's own AI key, the fact also carries the tokens and the list-price cost. They show on the Spend page as "StackJack-billed AI spend", beside the telemetry estimate and never added to it. A run on your own AI key carries no tokens and no cost here, because the vendor read for that key carries them. A run that a StackJack operator started for support makes no fact.

The source records facts only. It never records text: not the run summary, not an error message, not the trigger payload and not the tool-call rows. Its capture level cannot be raised above Facts only.

StackJack MCP tool calls

This source records the calls that your AI tools make through StackJack. Its capture level can be at most Scan only, so it never stores text. Scanning these calls against your data-loss rules is the Scan StackJack tool traffic setting. See Data-loss rules, findings and scanning StackJack tool traffic.

Two things that are not the same

  • Automations are recorded as AI use. This page is about that: a fact for each run.
  • Automations cannot use the AI Governance tools. An automation or a shared key cannot connect to the tools that read and change AI Governance from an AI tool. A governance decision is a person's decision. See Use AI Governance from your AI.

What you will see

  • The two sources on the All sources page, with the names "StackJack MCP tool calls" and "StackJack automation runs".
  • A fact for each automation run in the Activity explorer. The tool is shown as the automation.
  • The cost of runs on StackJack's key on the Spend page.

Troubleshooting

What you seeWhat to check
You cannot raise the capture level of one of these sourcesThey have a ceiling. Automation runs are Facts only. Tool calls are Scan only at most.
A run has no tokens or costThe run used your own AI key or a Foundry engine. The vendor read carries those figures.
A support run is missingA run a StackJack operator started for support makes no fact.

Next