Signed URL Delivery with Claude Code: MCP Tool Boundary

A production playbook for signed URL delivery in cross-industry operations using Claude Code: mcp tool boundary, run-scoped inputs, logs, typed results, and artifacts.

Audience: Teams shipping downloadable agent outputs

The problem

Teams shipping downloadable agent outputs need signed URL delivery to run repeatedly against artifact manifests, expiry policy, and customer permissions. In cross-industry operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.

Implementation path

Expose only the MCP tools needed for signed URL delivery, validate tool arguments, keep credentials in the owning service, and log each call outside the sandbox.

Tradeoffs and failure modes

Narrow tool boundaries reduce agent flexibility, but make the integration reviewable and supportable. For signed URL delivery, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.

Tool policy

tool: signed-url-delivery_lookup
agent: Claude Code
input_scope: /skill/.argo/inputs
credential_owner: broker
log_arguments: true
network_policy: allowlisted

Run this on Argo