Skip to content
Tools & Safety5 min read

Tool Connectors, Web Checks & Human Approvals

Connect internal ERP/WMS actions and live SearXNG web advisories with strict schema validation, read/write execution modes, and 2-hour idempotent approval cards.

Answering policy questions solves half the delay; checking live shipment status or logging a structured carrier exception completes the workflow—provided write actions never execute silently.

Two clear execution modes

Every connector in SCA's Tools Catalog explicitly declares its execution mode:

  • auto_run (Read & Verification Tools): Safe read lookups such as track_shipment, check_customs_status, or live web_search (via self-hosted SearXNG) run automatically when needed and record every lookup inside the expandable Checks performed log.
  • require_approval (State-Changing Write Tools): Actions that mutate records—such as log_carrier_exception or release_warehouse_hold—pause execution and emit a structured Approval Card directly in the thread.

Inside the Human Approval Card

Before any write executes, the coordinator sees:

  1. Exact target action name and structured field payload (shipmentRef, customer, exceptionType, summary).
  2. Approve or Reject action buttons right in the chat timeline.
  3. Cryptographic idempotency protection (requestHash + unique key) and a 2-hour approval expiration, ensuring stale pending actions cannot misfire days later and accidental double-clicks never create duplicate tickets.

Prompt-injection defenses on external content

External web snippets retrieved via SearXNG are wrapped cleanly as untrusted observation data inside tool outputs before synthesis—never promoted into trusted system instructions—while human approval gates prevent untrusted web text from triggering autonomous writes.