Pre-action authorization
Policy v2 evaluation, contextual risk classification, deny-overrides behavior, and fail-closed validation.
Security boundary
RuleOak controls actions only when they pass through RuleOak
RuleOak v0.10.2 is an application-layer authorization boundary. It evaluates supported routed actions before execution; it is not an operating-system containment layer.
In scope
Approval + execution binding
Human approval requests, action/policy-bound decision receipts, expiry, and one-time grant consumption.
Evidence
Redacted hash-chained events, checkpoints, evidence bundles, local reports, and bundle verification.
Guarded transports
Node.js guarded functions/tools, stdio JSON-RPC, MCP Streamable HTTP, and loopback REST authorization.
Out of scope
- Kernel-level syscall interception or operating-system sandboxing
- Malware detection, EDR, or complete data-loss prevention
- Complete prompt-injection prevention
- Endpoint identity proof, TLS termination, or enterprise identity federation
- Actions that bypass the guarded executor, SDK, CLI, gateway, or API
- Tamper-proof evidence against a privileged local actor that can replace policy, evidence, or signing material
Transport and SDK assumptions
For transport wrappers, RuleOak evaluates client-to-server action requests before they reach the guarded server. It does not observe side channels or traffic that bypasses the wrapper. For SDK use, developers must invoke the guarded wrapper rather than retaining and calling an unguarded executor.
Learning mode remains proposal-only
ruleoak protect --learn observes supported actions and can produce policy suggestions. No suggestion becomes active automatically, and critical hard blocks cannot silently turn into allow rules.
Deployment guidance
The REST authorization service is loopback-first. Non-loopback use requires explicit authentication, and external deployment should add TLS and a trusted reverse proxy. The built-in bearer token is a minimal deployment guard, not an enterprise identity service.