Parameter-Bound Human Approval
Typed Inter-Agent Sanitization Bus
Jump & context
Week 7: Parameter-Bound Approvals, Inter-Agent Bus, Production Containers & Inference Serving
The five hours
- 01
Concepts & system design
60 min· read · map the mechanismR41 — OWASP Agentic HITL & inter-agent trust
R22 — OAuth context binding
R21 — MCP context
R27 — OpenTelemetry trace correlation
Read the assigned sections; map the mechanism, threat model and trade-offs.
- 02
Project implementation
120 min· build · integrate · debugAdd human-in-the-loop (HITL) approval gates for consequential actions. Bind the cryptographic approval token to the exact
tool_name,target_resource, andcanonical_parameters_hash. *Lab:* Test TOCTOU (changing a parameter after approval) and approval replay.Implement
message-bus(D3) with typed envelopes (sender_id,recipient_id,workflow_id,provenance,trust_label,schema_version). Enforce capability separation so an untrusted research sub-agent cannot directly instruct a privileged execution sub-agent.Build, integrate, debug and improve the increment in the active project.
- 03
Security lab
60 min· attack your own systemNo separate task text for this block on day 37 — the sourced work sits in the block above. Keep the time box.
Test the abuse case, failure path, authorization bypass or resource limit.
- 04
Verification & evidence
30 min· test · record evidenceApproval TOCTOU/replay tests +
D3inter-agent spoofing and cross-workflow isolation test suite.Add or run regression tests; record the 9-point evidence record.
- 05
Deliberate practice & Socratic review
30 min· explain aloud · update gapsAnswer the 8 Socratic questions without notes: What? Why? How? What if? Why not? How can I prove it? Where can it break? What have I learned?
Re-explain the hardest concept aloud, inspect one edge case, update the gap log.
- total5 h
Read today · inside the concepts block
R21 R22 R27 R41Official specification: client/server lifecycle, JSON-RPC messages, tool discovery, authorization, and trust boundaries.
RFC 6749 core flows + RFC 9700 security best practices: narrow scopes, audience restriction, token leakage, and replay.
Traces, spans, context propagation, semantic conventions, and redacting sensitive attributes.
Agentic threat taxonomy: tool misuse, excessive agency, memory poisoning, inter-agent trust, and human oversight.
Read only the named sections needed for today's task. Reading sits inside the 60-minute concepts block; it is not extra time.
Free resources for this day
5 curated- docsOWASP · ~20 min readAI Agent Security - OWASP Cheat Sheet Series
Its human-in-the-loop section requires binding approval to actor, tool name, target resource, normalized parameters, timestamp and expiry — the parameter-bound approval token contract verbatim.
R41checked 2026-11-11 - videoLangChain · ~12 minLangGraph interrupt: Making it easier to build human-in-the-loop agents
Shows `interrupt()` pausing a graph, checkpointing state and resuming via `Command`, the pause boundary you attach an approval record to.
R21checked 2026-11-11 - videoGrabDuck! · ~20 minLangGraph Advanced – Use Dynamic Human in the Loop Interruption in Prebuilt AI Agents
Gates only risky tool calls dynamically and resumes after approve or cancel, which is the routing rule for which actions need a human gate at all.
R21checked 2026-11-11 - articleWorkOS · ~12 min readHow to add human approval to async AI agent actions
Treats an approval as a single-use token bound to a specific action with a short `requested_expiry`, the model for defeating approval replay and stale TOCTOU windows.
R22checked 2026-11-11 - labOpenAI · ~20 min read + codeHuman-in-the-loop - OpenAI Agents SDK
Implements pause/approve/resume with serialize state and explicitly warns that a transported approval snapshot must be integrity-checked, bound to the user and run, and made replay-proof.
R41moved 2026-11-11
Evidence record · 9-point standard
A lab is complete only when it produces evidence. Installing PyRIT, Garak, Presidio or TransformerLens is not completion. Saved on this device only.
Day notes
emptyThe two source formulations
verbatim · nothing summarisedProject & Deliverable Target
P3 (C5) | `D7` (OAuth Broker) & `D3` (Inter-Agent Sanitization Bus) | S6
Focus 1 (Parameter-Bound Human Approval — Orig. Day 47)
Add human-in-the-loop (HITL) approval gates for consequential actions. Bind the cryptographic approval token to the exact tool_name, target_resource, and canonical_parameters_hash. *Lab:* Test TOCTOU (changing a parameter after approval) and approval replay.
Focus 2 (Typed Inter-Agent Sanitization Bus — Orig. Day 48)
Implement message-bus (D3) with typed envelopes (sender_id, recipient_id, workflow_id, provenance, trust_label, schema_version). Enforce capability separation so an untrusted research sub-agent cannot directly instruct a privileged execution sub-agent.
Verification & Evidence
Approval TOCTOU/replay tests + D3 inter-agent spoofing and cross-workflow isolation test suite.
Read Today (60m Concepts Block)
R41 (OWASP Agentic HITL & inter-agent trust), R22 (OAuth context binding), R21 (MCP context), R27 (OpenTelemetry trace correlation).
---