The audit log wrote this entry for a Read of a PNG:
{ "outcome" : "blocked" , "posture" : "deny" , "method" : null , "failure" : { "kind" : "host_configuration" , ... } }
Enter fullscreen mode
Exit fullscreen mode
In the same run, the next request Claude Code sent to the model carried the image. A PDF and a notebook went the same way, and the notebook had the example key in plaintext. Three runs per file type, the same result every time.
Part 1 covers the setup and the method: Claude Code with its own model loop, the OWASP Agent Control Standard (ACS) reference Guardian, the shipped hook, and every protocol frozen with its sha256 before it runs. Part 2 is about the ! prefix, and part 3 about MCP tools. This part is about what the hook writes down when it can't carry out a decision.
Read goes through the Guardian now
Part 1 ended with a gap: the shipped hook settings didn't match Read, so cat of a file came back [REDACTED] and Read of the same file came back with the key.…