Governance at the Salesforce trust boundary.
Panopticore governs agent actions where they cross the network boundary. For Salesforce and Agentforce workflows, that means the callouts, integrations, and API calls that leave the platform.
Agent calls that leave Salesforce.
Governed by Panopticore
- Cross-platform calls leaving Salesforce
- Integrations to external systems triggered from Salesforce processes
- MuleSoft and other middleware orchestrations
- Outbound API calls from custom code, Apex, Flow, or agent actions
What happens at the boundary.
Agent in Salesforce triggers an outbound call to an external system (API, database, third-party service).
Panopticore intercepts at the boundary, authenticates the principal, and evaluates the request against policy.
Allow, block, or route to approval. The full session is recorded in a cryptographically signed Evidence Binder.
Where the highest-consequence actions happen.
When Salesforce agents act on external systems, those are the highest-consequence actions: data transfers, API calls to third-party systems, and cross-platform orchestrations. Route those calls through Panopticore and each one is under policy.
Further reading
Pre-deployment review, model evaluation, and prompt engineering all happen before the agent acts. Runtime governance happens when it acts.
Our NIST submission in plain language: the evidence gap, action-level risk, bypass-by-architecture, and governance independence.
Govern what crosses the boundary.
Request early access and we'll map your Salesforce egress surface together.