Option C: Docker Runtime Sidecar (Recommended for Kubernetes)
docker pull boundrix/sidecar:latest
# Run the local evaluation sidecar on port 8080
docker run -d -p 8080:8080 \
-e BOUNDRIX_ENV=production \
-e BOUNDRIX_POLICY_FILE=./policy.rego \
-v $(pwd)/audit.db:/data/audit.db \
boundrix/sidecar:latest
2. Initializing the Client & First Authorization Call
Connect your agent to the Boundrix decision engine in 3 lines of code:
from boundrix.client import BoundrixClient
# Initialize client pointing to local sidecar or centralized VPC cluster
client = BoundrixClient(base_url="http://localhost:8080", timeout=2.0)
# Evaluate execution boundary before executing a tool call
decision = client.authorize(
agent_id="agent-coding-01",
task_id="task-fix-auth-1029",
action="repo.read",
resource={"repo": "org/auth-service", "branch": "fix/token-expiry"}
)
if decision.is_allowed:
print(f"Action ALLOWED! Decision ID: {decision.audit_id}")
else:
print(f"Action DENIED: {decision.reason}")
3. Fail-Closed Execution Contract
Boundrix enforces a strict **fail-closed** contract:
• If the decision engine is unreachable due to network partition or DNS failure, the SDK raises `BoundrixConnectionError`.
• Agent frameworks **must treat any connection exception as an immediate DENY** and halt consequential tool execution.
Enterprise Capabilities
Task-Based Authorization: Scopes agent permissions strictly to the active delegated task objective and expires automatically.
Deterministic Tool Sandboxing: Evaluates tool actions against strict parameter allowlists before execution.
Real-Time Mid-Task Revocation: Halts rogue or drifting execution on the next tool call without terminating developer sessions.
Automated Secret Masking: Scrubs personal access tokens and cloud credentials from all recorded flight logs.
Boundrix is a runtime authorization and audit layer for autonomous AI agents developed by SASLabs. It enforces task-scoped execution boundaries so AI agents can complete their tasks without exceeding their delegated authority.
What is runtime authorization for AI agents?
Runtime authorization is the process of evaluating whether an autonomous AI agent is permitted to perform a specific action at the point of execution, using the agent's identity, delegated task, execution context, and current authorization state.
How does Boundrix differ from RBAC?
Role-Based Access Control (RBAC) grants broad, standing permissions to an identity. Boundrix evaluates task-scoped authority at runtime, checking whether a specific action is admissible for the active delegated task right now.
How does Boundrix handle agent delegation?
Boundrix creates a tamper-proof delegation lineage that links the human principal, the delegating agent, downstream sub-agents, and the task scope to ensure authority attenuates monotonically across multi-agent chains.
Can Boundrix revoke an agent’s authority?
Yes. Boundrix supports real-time mid-task revocation. When a task is revoked, any subsequent tool call attempted by the agent is immediately rejected.
Does Boundrix work with GitHub?
Yes. Boundrix's flagship initial use case secures AI coding agents interacting with GitHub, scoping actions to assigned repositories and branches while blocking destructive actions and credential exfiltration.
Does Boundrix run inside the customer VPC?
Yes. Boundrix is designed for in-VPC deployment via SDKs and lightweight container sidecars, keeping all policy decisions and source code within customer infrastructure.
How does Boundrix differ from prompt guardrails?
Prompt guardrails filter probabilistic text inputs and outputs. Boundrix enforces deterministic execution boundaries at the API and tool layer, ensuring unauthorized actions are blocked regardless of LLM reasoning or prompt injection.