Use AI Governance from your AI
People who hold an AI Governance role can use AI Governance from their own AI tool, such as Claude, Copilot or Cursor. They connect the AI tool to StackJack and ask about findings, usage, spend,…
Written By Christopher Scaminaci
Last updated 4 days ago
People who hold an AI Governance role can use AI Governance from their own AI tool, such as Claude, Copilot or Cursor. They connect the AI tool to StackJack and ask about findings, usage, spend, approvals, incidents, alerts and readiness. They can also make the everyday decisions, without opening the Portal. This page covers how to connect, the access setting, the built-in connector, how compact catalog mode reaches the tools, the tools by group and what the AI tool says when it cannot help.
The tools are the built-in AI Governance connector. It needs no key and nothing to buy.
At a glance
- What it does: lets a signed-in person read and act on AI Governance from an AI tool.
- Plan: every plan. A few tools need Business, as in the Portal.
- Who: a person who holds an AI Governance role and signs in with a second factor. An Administrator sets the access mode. An Auditor can read it.
- Where you set it up: AI Governance → Settings → AI assistant.
- Needs: StackJack added as a connector in the AI tool. The AI Governance connector inside StackJack is built in: nothing to set up and nothing to buy.
Connect your AI tool
Add StackJack as a connector in the AI tool and sign in when it asks. Your MCP endpoint and the guide for your AI tool say how. Sign in the way you sign in to AI Governance: through your organization's single sign-on, or with a second factor. Automations and shared endpoint keys cannot use these tools, because a governance decision is a person's decision. A second-factor sign-in counts for 30 days by default, and a connection that refreshes keeps its original sign-in, so a refresh does not renew it. When the sign-in is too old, the AI tool shows StackJack's refusal as the answer to your request. It does not start a new sign-in for you. To fix it, disconnect StackJack in the AI tool, connect it again, and sign in with single sign-on or a second factor.
Your organization's setting
Open Settings → AI assistant. Choose how AI tools may use AI Governance:
- Read and act. AI tools can read AI Governance data a person's role allows, and make the everyday decisions: decide a tool request, assign or close findings, open an incident, ask to see a name and acknowledge or resolve an alert.
- Read only. AI tools can read AI Governance data a person's role allows. Decisions, such as approving a tool request or closing a finding, stay in the Portal.
- Off. No AI tool is offered anything from AI Governance. Your governance data stays in the Portal.
Nobody has changed this setting until an administrator does, so the default applies: read and act.
Why the setting exists. An AI tool belongs to a third party. If your organization wants AI Governance data to stay in the Portal, for example by agreement with your works council or your data protection officer, switch it off here. The setting is the same on every plan.
Who can change it. Only an AI Governance administrator can change this setting. Every change is recorded in your audit log with the old and the new choice. An auditor can read it. An AI tool can never raise its own access.
The tools that exist today
The tools are one built-in connector, AI Governance. Every tool name starts with aigov_. There are 110 tools: 60 read and 50 change something. The role column says who can use each one. "Any role" means any AI Governance role.
The connector needs no key, no setup and no purchase. It is there whenever AI Governance is available to your organization, on every plan. Its calls are never counted as tool usage and never billed. It shows on the Connectors page as one "Built in" line, with a button to this page, and never as a card you add. Nothing here gives a person more than their AI Governance role and the access setting allow. Every call is checked again when it runs.
In compact and minimal catalog mode
Some AI tools can load only a limited number of tools, so StackJack offers a smaller catalog in compact and minimal mode. See Catalog modes. In those modes your AI tool does not list the AI Governance tools one by one. It reaches them through StackJack's catalog tools:
stackjack_search_toolsfinds a tool by what you ask for, for example "list open findings".stackjack_run_toolruns the tool it found.
The same checks apply as for a direct call: your role, the access setting, the second factor and the plan. If you are not admitted, the search does not find these tools at all.
Overview
Findings and alerts
Incidents
AI tools
Exposure scan
See AI exposure scan and Prospects.
People
Sources
Rules
Compliance
Gateway and storage
The tools that change something are offered only when the access setting is Read and act. Where an AI tool changes a setting, it makes the safe change: a new rule or rule pack starts in Test mode, a source is switched off but never on again, and a draft tells no one. Anything that widens collection, sends data out or changes who sees data stays in the Portal.
Deploy and manage
These tools do what the Deploy and manage tabs do. The Pro plan is needed for all of them. The library checks your access in the client on every call, in the same words the Portal uses, so a tool never does more than your role may. The Administrator-only items stay for an Administrator of the whole organization. See Deploy and manage.
An automation that an approval rule names reaches only three of these tools: aigov_list_pending_changes, aigov_get_deploy_run and aigov_decide_pending_change.
How answers look
A list comes in pages of up to 50 items, with a link to the Portal page that holds the rest. Text your own people typed, such as an incident summary or the reason for a request, is shortened in the answer, and the answer says so. Reading or deciding in an AI tool is not billed as tool usage. A decision is recorded in your audit log as made by the person who made it, exactly as it would be from the Portal.
Names
Staff names reach the AI tool exactly where your name policy shows them in the Portal. When names are pseudonymous, the AI tool receives the pseudonym, never the name, unless an approved reveal lets that person see it. No matched value or text of a prompt or an answer is ever sent to an AI tool. A finding shows its masked token, as the Portal does.
Asking to see a name from an AI tool only files the request. A second person approves or declines it in the Portal. The AI tool is never given the reason or the case reference that was typed with it.
What stays in the Portal
Some things stay in the Portal whatever the setting says: approving a name reveal, merging or splitting identities, pushing settings to endpoints, closing an incident, switching a source on, adding a person to a staff group that an alert policy or a rule names, putting a rule in Live mode, making or repairing the Microsoft partner app and signing in its service account, publishing a policy, downloading a report pack, exports and erasing a person.
Secrets never travel through a tool
No tool takes or returns an ingest token, a vendor key, a channel secret, an archive credential or a signing secret. Where a secret is needed, you create it in the Portal.
If your AI tool refuses
These are the answers a tool gives when it cannot help. Each comes with a fixed code the AI tool can read and, where a Portal page helps, a link.
- AI Governance is not available: "AI Governance is not available for your organization."
- Not set up yet: "AI Governance is not set up for your organization yet. Start it in the Portal."
- Connected with an endpoint key or an automation: "AI Governance tools act for a person. Connect your AI tool by signing in to StackJack yourself; automations and shared endpoint keys cannot use them." and "Connect this AI tool by signing in to StackJack (not with an endpoint key) to use AI Governance."
- The setting is Off: "Your organization has turned off AI Governance in AI tools. An administrator can change this in the Portal."
- The setting is Read only and a decision was asked for: "Your organization allows AI Governance reads in AI tools, but not changes. Make this change in the Portal."
- No AI Governance role: "You need a governance role for this. An administrator can grant one in the Portal." When you hold a role but not the one the tool needs, it says, for example, "You need the governance administrator role for this."
- No recent second factor: "Sign in to StackJack again from this AI tool to use AI Governance: through your organization's single sign-on, or with a second factor (for example an authenticator app)." The AI tool only shows this sentence. It does not open a sign-in. Disconnect StackJack in the AI tool and connect it again, then sign in the way the sentence says.
- A higher plan is needed: "This needs the Business plan or higher." The plan the feature needs is named. Some refusals say "This needs a higher plan."
- Something moved since you read it: "That request has already been decided or withdrawn. Read it again before making a change." The matching sentences cover an incident or a finding.
- A staff group that routes alerts: "That group is named by an alert policy or a rule scope, so adding a person to it would start sending that person's alerts, or applying a rule to them, with no one approving it. Add people to this group in the Portal." Removing people, and changing a group that nothing names, works from an AI tool.
- A connector hostname that does not serve AI Governance: "This tool is not served on the hostname this connection is using." It is the answer every connector tool gives on a hostname made for another connector. Reconnect on your organization's primary StackJack endpoint.
- Not found: "That record was not found in your organization." An alert, a request or an incident that is not in your organization, or not one your role may see, gets the same answer.
- A fault on StackJack's side: "AI Governance could not complete this request. Try again in a moment." After a decision or a change, read the record again before asking twice.
- A region that cannot take changes right now: "AI Governance cannot be changed right now in this region. Try again later."
Troubleshooting
Next
Was this helpful?
Still need help? Ask the team