Skip to content

Populate response_payload_hash in the forwarding path audit entries #293

Description

@imran-siddique

The AuditEntry schema carries response_payload_hash (SHA-256 of the canonical response), but the proxy's success path appends the final tool_call entry with request_payload_hash only -- the response hash is never populated. Surfaced by the industrial-embodied-ai example (agentrust-io/examples#16), which needs the audit bundle to bind the controller outcome, not just the request.

Fix: hash the post-scan response content (the same bytes the egress check sees) and include it in the step-6 audit append in proxy.call_tool.

Generated with Claude Code

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions