Customer-operated execution controls

Execution control for AI agents.

Sabrix helps platform teams govern consequential agent actions through request-bound approvals, coordinated dispatch and durable execution records inside their infrastructure.

For supported actions routed through your configured execution integration.
scenario // five agents · one refund request ● ILLUSTRATIVE WORKFLOW
Illustrative Operation rf_9402 · $2,450.00 USD
Five workers share one refund operation. Who receives dispatch permission?

Target: acct_8829 · Human approval required above $500.00.

✕ Unenforced Dispatch (Illustrative)
5 workers dispatch the refund independently.
Illustrated outcome: $12,250.00 across 5 refunds.
✓ With Sabrix (Illustrative)
One registered operation waits for approval (HTTP 202). After approval, 1 claim wins; 4 get HTTP 409 Conflict.
Illustrated outcome: one $2,450.00 refund.
Interactive Explainer: Canonical Parameter Binding SIMULATION: APPROVED
POST /v1/refunds amount: to: acct_8829
Illustrative baseline ($2,450.00): Approval binds to the exact request in the configured integration. Edit the amount above to simulate parameter tampering.
Explore illustrated approval, race and timeout scenarios.
Explore 60s Tour →
In-VPC Local Proxy Routing
Mediates agent traffic locally under your routing policy without external SaaS hops
Fenced Duplicate Suppression
Suppresses duplicate redispatch and fences retry storms for registered operations
Brokered Credential Vaulting
Downstream credentials vaulted at gateway when brokered injection configured
Compact Native Rust Sidecar
Low idle memory footprint designed for transparent sidecar deployment in Kubernetes pods
Enforcement Layer

Safeguards for the configured action path.

Sabrix combines configured credential brokering with request-bound approvals and durable dispatch coordination for supported actions.

CREDENTIAL SAFETY

Brokered Provider Credentials

With credential brokering configured, agents request supported actions without receiving the provider's production credentials. The gateway applies policy before injecting the stored secrets.

REQUEST-BOUND APPROVAL

Request-Bound Human Approval

Hold supported sensitive actions for manager review. Approval binds to the exact request so altered arguments cannot reuse it. A review threshold differs from a hard spending cap.

CONCURRENCY SAFETY

Durable Duplicate-Dispatch Fencing

When workers share one registered operation, Sabrix coordinates dispatch permission and fences competing claims. A winning claim permits dispatch; the provider result establishes the outcome.

CRASH & TIMEOUT SAFETY

Uncertain Outcome Quarantine

An interrupted request can leave its outcome unknown. Supported execution paths retain the record and fence automatic redispatch while the operator reconciles with the destination.

Incident Risk Patterns

What recent incidents teach us about agent boundaries.

These reports illustrate risks at agent boundaries. Each simulator link demonstrates a related Sabrix control through an example workflow, with customer infrastructure responsibilities stated below.

EGRESS SEVERANCE EXAMPLE: HTTP 403

OpenAI Evaluation Agents Reached Hugging Face

July 2026 · OpenAI Report

Incident: Evaluation agents with reduced safeguards initiated unauthorized outbound network calls to test infrastructure.

Related Control: Configured egress rules reject unapproved destinations, including metadata endpoints such as 169.254.169.254.
Customer Boundary: Requires container network routing to enforce that agent egress cannot bypass the proxy.
CONCURRENCY FENCING EXAMPLE: HTTP 409

Claude Code Chained in Multi-Target Attacks

Nov 2025 · Anthropic Threat Intel

Incident: Attackers manipulated agent tooling into firing automated, parallel reconnaissance chains across ~30 organizations.

Related Control: Tool allowlists constrain permitted actions and destinations. Dispatch fencing coordinates retries that share one registered operation.
Customer Boundary: Governs external network calls and tool APIs; local shell commands require OS sandboxing.
VAULTED APPROVALS EXAMPLE: HTTP 202

Agent Action During Permissive Testing

July 2026 · UK AISI Report

Incident: During permissive testing with internet access enabled, an agent attempted unauthorized external operations.

Related Control: Credential brokering keeps configured provider secrets at the gateway. Request-bound approval can hold supported sensitive actions for manager review.
Customer Boundary: Effective when agents access external tools exclusively via the brokered gateway socket.
Adoption Path

Two Integration Paths: Model Traffic and Agent Actions

Route supported model requests through the proxy. Separately configure the action integration, identity, approvals, retained authority and destination for consequential external actions.

Model API Routing

Route Supported Model Traffic

Configure a supported model client's OPENAI_BASE_URL and required credentials to route traffic through the proxy. Validate inspection and PII behavior for your provider and traffic.

SCOPE: Supported model API routing
EVALUATION: Your provider and routing configuration
External-Action Execution

Durable In-VPC Execution Controls

Deploy the Rust gateway with retained authority storage inside your infrastructure. Configure the supported action integration, identity, approvals and credential brokering.

DEPLOYMENT: Customer-operated gateway with retained authority
EVALUATION: One supported action and agreed success criteria
Enterprise Evaluation

Evaluate an agent action in your infrastructure

Discuss one workflow with the founder and agree on the identity, approval and provider requirements for a bounded evaluation.