mrhid6
2e3d2a33f9
CreateWorkflow and UpdateWorkflow validated TargetServerIDs against the caller's scope but never checked TargetTags, letting a restricted token save a workflow with an empty ID list and an out-of-scope tag selector, then reach those hosts once the scheduler fires it as the system with no restriction of its own. Add validateWorkflowTargetScope, applying the same all-or-nothing rule the MCP create_workflow tool already enforces: resolve the full target set unscoped and scoped, refuse unless they match. Update the PUT /api/workflows/:id/schedule fleetWide comment to say why it is safe now (targets are constrained at write time) rather than repeating the falsified claim that scheduling reaches nothing new.