[Bug] False-positive safety blocking rejects benign local Codex commands

[TomerGamerTV]

What happened?

Benign Codex Native commands are sometimes rejected by the automatic safety layer.

When this happens, the assistant reports messages such as:

The broad content scan was blocked by the automatic safety layer.

The problem is not limited to broad filesystem searches. After narrowing the request, even harmless commands such as Get-Location can still be rejected.

This prevents Codex from performing basic local inspection even when the requested operation itself is benign.

Steps to reproduce

1. Start a Codex Web session with local/native tool access enabled.
2. Ask Codex to inspect a local configuration location.
3. Codex attempts a filesystem/configuration search and the operation is rejected by the automatic safety layer.
4. Retry with a narrower operation.
5. Even a harmless command such as Get-Location may still be rejected.

Expected behavior

Clearly benign local commands should be allowed.

If a particular command or operation is considered unsafe, the rejection should be limited to that specific operation rather than causing unrelated, harmless commands to be blocked as well.

Actual behavior

Multiple increasingly narrow commands can be rejected by the safety layer, including commands that do not access sensitive information.

Once this happens, Codex may be unable to perform local inspection at all and has to fall back to external sources instead of inspecting the local environment.

Reproduction frequency

Intermittent, but multiple commands in the same session can be affected once the issue occurs.

Additional context

The issue appears to be a false-positive in the safety/approval layer rather than a failure of the underlying command itself, because even basic commands such as Get-Location can be rejected.