SD-026 — Codex Unrestricted Sandbox
SD-026 flags danger-full-access in supported Codex TOML, including declarations in inline profiles ignored by the supported project-local loader.
What it matches
An explicit sandbox_mode = "danger-full-access" declaration at the root or in an inline profile of .codex/config.toml or .codex/*.config.toml.
Why it matters
If the effective Codex runtime activates this declaration, commands run without Codex sandbox restrictions. Repository configuration alone cannot establish project trust, profile selection, source precedence or managed requirements. The finding does not prove that the runtime is unrestricted.
Example
toml
# .codex/config.toml [profiles.review] sandbox_mode = "danger-full-access"
This inline profile declares unrestricted access but is ignored by the supported Codex project-local loader. The finding inventories the declaration, not an active runtime policy.
How to fix it
Prefer read-only or workspace-write where appropriate. Review the actual trusted configuration, selected profile and managed requirements before relying on runtime isolation; changing a repository declaration alone does not establish the effective policy.
Known false positives
A deliberately unrestricted setup, or a dormant profile that is never selected. This reports a declaration, not proof that a trusted runtime activates it.
Standards mapping
OWASP ASI ASI03
CWE CWE-732
Check your own skills
Scan a repository or a single skill against this rule and the rest of the catalogue, free.