Tag
telemetry
15 entries, including 7 patterns.
The hook went quiet; traffic did not
An inline AI policy can be configured and healthy-looking while requests pass uninspected. Measure enforcement coverage, not just denials.
- Pattern
Verdict Coverage Accounting
Join independent request counts to hook verdicts and configuration state so silent inspection gaps are observable and high-impact actions stay gated.
- Pattern
Evidence-Bound Callback Completion
Accept a completion as a scoped claim, then verify independent evidence and current authorization before the next side effect.
The callback said done
A workflow completion token can close a task without proving that the approved work happened. Verify the result at the boundary before an agent acts on it.
The trace sampler erased the denial
A security decision cannot be audited from a trace that was never exported. Keep a narrow action ledger outside the sampled observability path.
- Pattern
Unsampled Action Receipt
Preserve gate decisions and target outcomes even when agent traces are sampled out or filtered.
- Pattern
Telemetry-as-Evidence Incident Gate
Let an assistant inspect attacker-influenced logs without allowing their prose to close incidents or authorize response actions.
The log line became an incident command
An investigation assistant can read an honest log record containing an adversary's words. Keep telemetry as evidence, not authority.
- Pattern
Replay-Fenced Agent Side Effects
Give one approved intent one durable target-side identity, regardless of workflow retries, forks or restarts.
- Pattern
Revocable A2A Push Subscribers
Make a task's outbound update subscription expire with its subscriber's entitlement, including queued retries.
The checkpoint did not undo the transfer
Replaying an agent workflow can repeat a real-world action unless the target recognizes the same operation.
The webhook kept listening
An A2A task can keep sending updates to a once-authorized subscriber after that subscriber loses access.
- Pattern
Cross-Boundary Action Evidence
Correlate policy, dispatch and target events without confusing transport success with business outcome.
The trace ended at the tool call
Detection fails when the agent, gateway and target each describe only their own success.
Logging that lies
A green success log is not proof that a policy gate ran.