Approval-hook pattern: external source-rights evidence for URL-bearing tools #81

AgentLayer’s separation between tool interfaces, executors, and approval hooks makes it possible to inject external evidence without changing individual tools.

For URL-bearing web/research tools, one useful approval context could be a signed source-rights observation.

AcqPath observes machine-readable source-rights/TDM declarations for a public URL + intended purpose and returns a signed, timestamped receipt. It does not grant a license or legal clearance.

A provider-neutral approval-hook pattern could:

• inspect the proposed tool call before executor dispatch;
• fetch external evidence for URL + purpose;
• attach provider / timestamp / declaration state / receipt digest to the approval context;
• let the human/policy hook decide whether execution continues;
• retain the evidence reference with the resumable run history.

Would this fit AgentLayer’s approval-hook model as an example or extension recipe? I can provide a minimal fixture against the existing tool interface/executor separation.