Skip to content

connection_sync

Sync one connection (cx-...) now (contract 1.17): the deployment runs its source at the scheduler’s next tick, whatever the schedule, off included. A signed connector.sync command, audited exactly as Sync now on the connection’s card; while one sync is in hand, asking again returns it. A client administrator only, signed in at their own keyboard: refused for a machine key, a delegated token and AAL staff, and until the client switches connector.sync commands on.

Role: client_admin, as a person signed in at their own keyboard (a machine key, a delegated token and AAL staff are refused, as on the API’s route); acts: sends a signed handler command and is audited, with via: mcp.

Acts: yes. It sends a signed command for a client administrator at their own keyboard, and is audited; a machine key and a delegated token are refused.

Input Type Default
id string required
card string or null null
deployment string or null null
reason string or null null

The arguments of a tools/call request:

{
"name": "connection_sync",
"arguments": {
"id": "<id>"
}
}