Govern the action, not the session
Each semantic action is authorized against attenuated authority in real time. A valid session is not a blank check.
Product · AI Action Control Plane
Put a control point between agent intent and real-world execution.
RaksHex turns an agent request into a governed action: identify the actor, resolve delegated authority, evaluate policy, mediate the credential, and preserve the resulting decision evidence.
Governed action receipt
actorsupport-agent-prod
actionfinancial.refund
requested$400
authorityrefund ≤ $50
decisionDENY
credentialNOT RELEASED
ledger0x8f7a21c4
Action Control
Evaluate a semantic action against policy and delegated authority before execution.
Delegated Authority
Parent-to-child authority can preserve or narrow scope, but cannot silently expand it.
Credential Broker
For brokered execution, a DENY prevents the requested credential from being released.
Action Ledger
Record decision context in a hash-chained ledger designed to make tampering evident.
Private-beta rule: begin with one agent and one consequential action. Expand only after the authority map and decision evidence are understood.
Built-in capabilities
The Agent Firewall core, piece by piece: how an action gets authorized, delegated, enforced, and recorded.
Semantic actions
Policy is written against what an agent is doing, not the HTTP call underneath it.
- Actions like financial.refund, not raw endpoints
- One policy model across providers
- SDK-based integration into your agent's call path
- No proxy re-architecture required to get started
Semantic Action Authorization
Evaluated// Authorize a semantic action
const decision = await firewall.authorize({
action: "financial.refund",
authority: delegatedAuthority,
});
Architecture Comparison
Session-Level vs Action-Level Control
Drag the handle to compare governing who has a session against governing what each individual action is actually allowed to do.
RaksHex Agent FirewallAction-Level
Enforcement Active
Semantic action authorizationEnforced at the credential
Delegated AuthorityActive
Parent-to-child attenuation — a child authority can never exceed its parent's scope.
Enforced
Credential MediationBroker
A DENY blocks the credential itself — the secret never reaches a denied caller.
Fail-closed
Action LedgerHash-chained
Every decision is recorded tamper-evidently for audit and dispute resolution.
Tamper-evident
Why Teams Move Past Session-Level Auth To RaksHex
A valid API key or session token proves who is calling — not whether this specific action, right now, should be allowed.
Govern the action, not the session
Every semantic action is evaluated against the caller's actual delegated authority, not just whether the session is valid.
A DENY that actually denies
Enforcement happens at the credential broker, so a blocked action can't fall back to a raw API key that still works.
Evidence you can hand to an auditor
The hash-chained Action Ledger gives you a tamper-evident record of every authorization decision, not a log you have to trust.
The credential broker mediates every brokered request. A DENY blocks the secret from ever reaching the caller — enforcement lives at the same layer as the credential, not in a dashboard someone has to watch.
Supported Providers
One Policy Model, Every Provider
The same semantic action and delegated-authority model applies regardless of which LLM provider or coding agent is making the call.
RaksHex Agent Firewall
Action Authorization & Policy Engine
OpenAI
LLM ProviderAzure OpenAI
LLM ProviderAWS Bedrock
LLM ProviderGoogle Vertex / Gemini
LLM ProviderGitHub Copilot
Coding AgentCursor
Coding AgentOpenAI-Compatible
Self-Hosted / CustomOne system of record
Security, FinOps, and developer access should agree on what AI is running.
Point tools solve isolated pieces. RaksHex connects authorization, credential mediation, and evidence so the same answer holds up in an engineering review, a finance review, and an audit.
Deny at the credential
The credential broker mediates brokered requests. A DENY blocks the secret from reaching the caller.
Enforce at runtime
Evaluate provider and model rules, budgets, tool policies, PII redaction, injection signals, and kill switches before execution.