FrootAI.dev AgentSpace
On this page 4
Design & Extend Worker + D1

Connector Exchange & secret references

Control external data paths with action-level policies, exact HTTPS origin allowlisting, and zero-custody secret bindings.

Status: Available Architecture: F · Foundations Read: 6 min Verified: 2026-11-16

Action policies: read, write, destructive

Connector Exchange treats every external tool or model integration as an explicit authority boundary. Actions are classified into three risk tiers:

Action tier Default posture Examples
read Allowed within allowlisted scopes Search approved SharePoint site, read GitHub check status, fetch CRM opportunity summary.
write Ask first (requires Decision Gate or human confirmation) Create draft knowledge page, open pull request, post status comment.
destructive Disabled by default Delete records, revoke production bindings, archive shared channels.

Exact HTTPS origin allowlisting

In remote Worker mode, outbound connector calls are validated against the OUTBOUND_ORIGINS environment allowlist before any network socket opens:

  • Non-HTTPS origins are rejected outside ENVIRONMENT=local.
  • Connector base URLs must match an approved origin in OUTBOUND_ORIGINS exactly (scheme + host + port).
  • Action-specific webhook paths are resolved safely and cannot redirect or override the approved origin host.
  • Upstream responses are bounded to 256 KB with a strict 15s request timeout.

Secret references without secret custody

AgentSpace never stores raw API keys, OAuth tokens, or connection strings inside workspace JSON, D1 tables, audit logs, or Queue payloads. Instead, connectors bind to a Secret Reference:

{
  "alias": "foundry-model-prod",
  "provider": "worker_binding",
  "bindingName": "CONNECTOR_FOUNDRY_API_KEY",
  "metadata": {
    "purpose": "Approved model runtime",
    "rotationOwner": "platform-ops"
  },
  "expiresAt": "2027-03-01T00:00:00.000Z"
}
Schema-enforced secret rejection

If a client mistakenly includes fields such as apiKey, token, secret, or password inside metadata, the API rejects the request with 400 validation_error before persistence.

Catalog breadth vs executable adapters

The Connector Exchange UI displays enterprise templates (Microsoft 365 Work Graph, Foundry, GitHub, Azure DevOps, ServiceNow, PostgreSQL) to model governance scopes and data paths. In the current v0.2.0 Worker build, live remote execution supports the verified webhook and OpenAI-compatible HTTP adapter types; non-bound templates remain clearly labeled as preview/modeling entries.

Verified against repository suites
tests/backend/jobs.test.tstests/backend/platform.test.ts
Markdown specification

Connector Exchange & secret references