What happened
Morty invoked send_message_to_agent; Meeseeks read and returned restricted memo values; Morty wrote and published them to the group.
2026-11-06
HighPrimaryGreyZone researchers report a controlled Clawith episode where claimed approval and agent-to-agent delegation exposed a restricted acquisition memo.
What happened
Morty invoked send_message_to_agent; Meeseeks read and returned restricted memo values; Morty wrote and published them to the group.
Why it matters
No production impact established. The controlled episode exposed the memo's bid ceiling, counterpart contact and deadline outside the configured boundary.
Missing authorization check
Authenticated recipient-specific disclosure authority preserved and verified across agent-to-agent delegation, workspace writes and group replies.
Would PP block it?
This depends on mediating both agents' disclosure operations and preserving original-requester provenance. The paper does not test Permission Protocol.
Incident analysis
2026-11-06
GreyZone v1 reports the controlled Clawith episode and oracle-verified disclosure.
Authorization boundary
This incident is categorized as Governance bypass. The relevant Permission Protocol gate is Tool-Call Gate. The read is conditional: the block only applies where the real action boundary is routed through a gate.
An integrated independent disclosure boundary could require verified authority instead of a requester's quoted approval.
Related incidents and controls
Start small
This incident maps to Tool-Call Gate. Start with the boundary that controls the actual action, then require a signed receipt before execution.