AI agent governance. Govern what your teams' AI agents can do.
Control how your teams use AI agents across business systems, with security policies and audit logs in one place.
INV-2041NetSuite -
Lena OrtizFinanceChatGPT
Allowed Returns the vendor bill.Decided byConnector accessFinance shares this NetSuite account -
Priya ShahProcurementClaude
Masked Returns the bill with bank details hidden.Decided byTool PoliciesProtect bank details · Enforce -
Sam RiveraOperationsClaude Code
Refused Sam left yesterday. The call is refused.Decided bySSO and SCIMDeactivated in Okta
Enterprise MCP governance. Take your AI rollout from the pilot team to the whole organisation.
Your identity provider sets who is in, groups carry access, and each system's owner decides who connects.
Configure access. Set access for teams and individual users.
Choose who can connect each system, who can use shared connections, and what their agents can read or change.
Connector profile
Connection setup and available actions
The new connection uses this profile's action selection.
Connected account
An existing connection to a business system
Account Members can run its available actions.
Policies apply when an agent acts for a member
Assign further restrictions to users or groups with account access.
Explore Tool PoliciesSync members and groups from your directory. Manage their access grants in StackOne.
Explore SSO and SCIMChoose accounts and available actions
Define actions through connector profiles. Share profiles for new connections, or grant access to accounts already connected.
Explore Connector AccessSet rules for member-based calls
Use Tool Policies to restrict tools, prevent changes to protected fields or mask returned data.
Explore Tool PoliciesKeep personal data out of tool calls
Add a Redact PII rule to redact or block email addresses, phone numbers, SSNs and card numbers in what agents send and read.
Explore PII RedactionAI agent governance case study. Nine business systems connected inside two weeks, with access granted per linked account.
A US medical research organisation ran its first live agent query on the day it signed, then connected systems from identity and device management to procurement and finance.
Healthcare · Customer story "The granular access at the account level for a connector is a huge help. So now I feel confident that we can create connectors to everything."
Authentication and response protection. Protect credentials and check tool responses.
StackOne authenticates calls to business systems. Enable Prompt Injection Guard to inspect returned content for prompt injection.
The leading prompt injection model checks responses before your agent reads them.
Explore Prompt Injection GuardAudit logs and SIEM export. Keep every tool call on record.
Review tool calls, setup changes and sign-ins in action, platform and sign-in logs. StackOne records action logs by default, with no setup.
| User / Agent | System / Action | Outcome / Checks |
|---|---|---|
| Taylor Brooks | SAP S/4HANA | 200 2 Clean |
| Noah Patel | Jamf Pro | 200 2 Clean |
| Alex Morgan | Workday | 200 3 Clean |
| Lena Ortiz | Salesforce | 200 2 Clean |
| Priya Shah | Xero | 403 3 Not run |
| Sam Rivera | ServiceNow | 201 2 Clean |
| Alex Morgan | Workday | 200 3 Clean |
- User / Agent
- Taylor Brooks
via Copilot
- Account
- Supplier Admins
- User / Agent
- Noah Patel
via Claude Code
- Account
- IT Support
- User / Agent
- Alex Morgan
via Claude
- Account
- People Operations
- User / Agent
- Lena Ortiz
via Copilot
- Account
- Revenue reporting
- User / Agent
- Priya Shah
via Claude Code
- Account
- Finance
- User / Agent
- Sam Rivera
via Claude Code
- Account
- IT requests
- User / Agent
- Alex Morgan
via Claude Code
- Account
- People Operations
Send action and platform logs to your SIEM
Run a small collector or proxy that pulls records from the Logs API and forwards them to any SIEM or data platform. The Logs API is included in Gateway Enterprise and both OEM plans, and audit logs and SIEM export are Enterprise features.
Deployment and compliance. Choose the deployment that fits your requirements.
Compare managed cloud with regional projects, a dedicated account and self-hosting.
Plan residency and operations
Discuss where StackOne runs, who operates it and how encryption keys are managed.
Explore DeploymentRestrict StackOne API access by source IP
Choose which IP addresses can call a project's StackOne API: single addresses, ranges or CIDR blocks.
Explore IP allowlistingSOC 2 Type II security review. Evidence for your security review.
"As a company rooted in security assurance, we needed a partner sharing our priorities. StackOne's approach gave us confidence to scale without compromise."
SOC 2 Type II
Request the report, and review subprocessors and security information, in our trust center.
Visit the trust centerFAQ. Questions about AI agent governance
See how StackOne fits your AI rollout.
Talk through the systems your teams use and the controls your rollout needs.