interrupt_v2_task

Returns the updated task and native status and whether committed effects remain. Check interruptible and control permission first. An unsupported task or completed publication requires inspecting the task and its evidence.

These signatures come from local MCP tool discovery. Use the signature registered by your deployment and confirm your identity and permissions before calling the tool.

Endpoint signatures and example arguments

Examples show the arguments to the tool. Replace placeholder IDs and illustrative revisions with values from your authorized disposable scope.

{
  "task_id": "{{task_id}}"
}

{
  "properties": {
    "task_id": {
      "title": "Task Id",
      "type": "string"
    }
  },
  "required": [
    "task_id"
  ],
  "title": "interrupt_v2_taskArguments",
  "type": "object"
}

{
  "workspace_id": "{{workspace_id}}",
  "application_id": "operating-cube",
  "task_id": "{{task_id}}"
}

{
  "properties": {
    "workspace_id": {
      "title": "Workspace Id",
      "type": "string"
    },
    "application_id": {
      "title": "Application Id",
      "type": "string"
    },
    "task_id": {
      "title": "Task Id",
      "type": "string"
    }
  },
  "required": [
    "workspace_id",
    "application_id",
    "task_id"
  ],
  "title": "interrupt_v2_taskArguments",
  "type": "object"
}

Handling errors

MCP_TOOL_CAPACITY_NOT_DISPATCHED means the server did not dispatch this call. MCP_TOOL_DEADLINE_OUTCOME_UNKNOWN or MCP_TOOL_PROCESS_FAILED_OUTCOME_UNKNOWN leaves the outcome unknown. For a call with effects, reconcile the original request before starting a new one. For a scoped denial, verify the caller's grant and the selected target.

Module guidelines · Related workflow · Application-language function catalog