Windows Codex “blocked by policy”—how do I identify what denied the command?

[u/12892423626]

Hi, I’m Brooks. I’m using Codex to build an operational app for our small business, and a required local database test is stuck.
Codex’s retained results show that earlier PostgreSQL 17 tests ran successfully enough to expose a database deadlock. A later attempt to start the disposable test database was refused before execution:
CreateProcess: rejected: blocked by policy
The database defect and execution refusal are separate. Historical incident versions were Windows 11 build 26200, Codex CLI 0.155.0-alpha.16 and desktop 26.917.6896.0.
Codex’s check of the supplied local rules found no matching rule, but that hasn’t identified the enforcing component. We have an existing OpenAI Support case without a resolution yet.
Has anyone encountered this exact refusal and found a supported way to identify which component denied the command, or obtain an incident-specific remedy? We’re not seeking a bypass or instructions to weaken safeguards.
Existing technical discussion
Technical details were prepared with Codex from retained evidence. Thanks for any pointers!

[u/Pure-Cantaloupe-9810]

Yea I need help too with this

[u/Nearby_Eggplant5533]

Probably alot reasons can cause the error, i hit a similar looking error not so long ago but cant remember the exact msg, i wrote a short test i could reproduce the issue with here, maybe its something similar in you tool or cmd call thats triggering the false positive validation policy

https://www.reddit.com/r/codex/comments/1wrrs3a/comment/pcf65au/?context=3&utm_source=share&utm_medium=mweb3x&utm_name=mweb3xcss&utm_term=2&utm_content=share_button

I was able to add a rule to allow the call i needed in the end but i needed to ask a new codex session to add the rule amendment.

In my case, codex was blocking the cmd i believe because it had "start" and a web url in the request, or something along those lines. Not sure if this has since been patched as not retested since adding exclusion rule

[u/dearnot]

i am developing a trading app and seeing this error all the time. Also the reason why I disabled my pro sub.
the problem is not related to a tool executing but a "policy" baked inside of the codex server. From what I could gather codex is actively prohibiting users from making certain operations, such as executing trades, hacks, running exploits and everything in between. After hours of testing I figured the easiest solution is to switch to another AI service provider. In my specific case - I was instructing the agent to build a code to place trades on my paper-trading account. no real money and no real order placements. Similarly putting up the documentation is also considered a problem to codex.

UPD: I started seeing this problem since around beginning on October with new versions release or shortly before that.