Connectors · the enforcement plane
The gate verifies. Not us.
Connectors live in the target systems your agents act on. They verify the Authority Token presented to them — signature, TTL, intent hash, revocation — before the action proceeds. If anything is off, the action is refused there.
02 · Connectors
workflow_dispatch · single-use
Authority-bound workflow triggers. Token verified at the action boundary. Workflow run ID linked back to the audit chain.
incident · change request
Token-bound incident creation and change requests. Approval state preserved against the issued token.
payment · refund · subscription
Authority-bound payment actions. Single-use tokens prevent replay; refunds verified against original authority chain.
tool calls · across MCP servers
Every tool call through MCP is authority-gated. Compatible with any MCP-speaking client.
incident · trigger · resolve
Authority-bound incident actions over the REST and Events v2 APIs. Host-pinned, token-gated at the boundary.
event · monitor mute
Region-aware, host-pinned adapter. Events posted and monitors muted only against a verified Authority Token.
message · channel lookup
Bot-token adapter pinned to slack.com. Messages post only after the token verifies at the gate.
user suspend · unsuspend
SSWS-token lifecycle actions, host-validated to your Okta org. Every action is authority-bound.
user enable · disable
Microsoft Graph adapter, host-pinned to graph.microsoft.com. Lifecycle actions gated at the boundary.
secret read · rotate
KV v2 adapter for self-hosted Vault. SSRF-hardened; secrets read or rotated only under a verified token.
case create · update
OAuth refresh-token adapter, both hosts pinned to salesforce.com. Case writes escalate under the starter policy.
IAM binding · instance stop
Service-account JWT-bearer OAuth, pinned Google API hosts. Privileged writes are authority-gated.
worker hire · time-off approve
OAuth refresh-token adapter over the Workday REST API, tenant hosts pinned. Every write is token-bound.
purchase order · invoice
OAuth client-credentials adapter. Purchase orders and invoices post only against a verified Authority Token.
IAM policy attach · instance stop
Hand-rolled SigV4 signer, region-scoped IAM/EC2. Privileged actions are authority-bound at the boundary.
Every connector above is Beta, not GA. The adapter code is real, token-gated, host-pinned, and covered by hermetic tests — but each is validated against live provider credentials only once an owner connects a real account. See the Capability Truth Matrix for the exact status of each.
03 · What every connector verifies