connection_schedule

Set how often one connection (cx-...) syncs (contract 1.17): mode off, every_15m, hourly, working_hours (needs tz) or daily (needs at, 24-hour HH:MM, and tz, an IANA zone such as Europe/London). Sent to the deployment as a signed connector.schedule command, checked and audited exactly as on the connection’s card; asking again for the schedule already asked for sends nothing. Name the source with card (<pack>:<card>) where the deployment reports more than one. 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.schedule 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.

Inputs

Input	Type	Default
id	string	required
mode	string	required
at	string or null	null
tz	string or null	null
card	string or null	null
deployment	string or null	null
reason	string or null	null

Call

The arguments of a tools/call request:

{
  "name": "connection_schedule",
  "arguments": {
    "id": "<id>",
    "mode": "<mode>"
  }
}