Logistics: Freight Exception Review with Claude Code: MCP Tool Boundary
A production playbook for freight exception review in logistics operations using Claude Code: mcp tool boundary, run-scoped inputs, logs, typed results, and artifacts.
Audience: Logistics operations teams
The problem
Logistics operations teams need freight exception review to run repeatedly against tracking events, bills of lading, invoices, carrier notes, and exception policies. In logistics 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 freight exception review, 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 freight exception review, 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: logistics-freight-exception-review_lookup
agent: Claude Code
input_scope: /skill/.argo/inputs
credential_owner: broker
log_arguments: true
network_policy: allowlisted
Run this on Argo