How one request to example.com:443 is decided
The authorizer walks five questions for op(action=net:connect:tcp, resource=net:domain:example.com:443) in the sandbox m101-policy. A matching deny rule ends in Denied by local rule with deny_kind explicit and rule local:<uuid>. Organization governance was inactive on the capture host, and when active only organization allow rules grant access. A sandbox-scoped allow or a global or kit allow returns allowed true, as the checks for example.com and api.anthropic.com show. When nothing matches, the result is No matching allow rule with deny_kind implicit, and the sandbox sees an approval request.
THE REQUEST
op(action=net:connect:tcp, resource=net:domain:example.com:443) · context sandbox:m101-policy
a deny rule matches?
any scope, any source
Denied by local rule
deny_kind: explicit · origin: local
rule: local:<uuid> · 09-check-deny.json
no
org governance active?
governance.active
false on the capture host
when true, only org allow rules grant
local and kit allow rules go inactive
a sandbox allow matches?
scope sandbox:m101-policy
allowed: true
local <uuid> example.com [tcp]
09-check-allowed.json
a global or kit allow matches?
local-policy, kit:<name>
allowed: true
default-ai-services api.anthropic.com:443
03-policy-check-anthropic.json
nothing matched
default deny
No matching allow rule (default deny)
deny_kind: implicit · 09-check-verbose.json
inside: Approval required for example.com:443