Skip to content

Request approved execution

Describe the guardrails a data-changing request needs before Engine performs a synchronisation. Guide-derived workflow; compare with the current six-tool MCP surface.

This is an operational workflow, not an additional callable MCP tool. See the six current tools.

Operator question

Is this exact operation approved for this target and window?

The guide treats orchestration and sign-off as visible operational steps rather than disconnected scripts.

Context a call would need

  • Approved operation and target
  • Actor and approval reference
  • Execution window and idempotency context

Evidence to return

  • Accepted or rejected request
  • Execution identity and timestamps
  • Progress and result provenance

Safety and availability

No current MCP tool executes SQL or starts a synchronisation. This is a future control requirement, not an available function.

SQL table synchronisation guide