A transit maintenance agent chains tools to open work orders outside intended service zones. What should the purple team report?
Select an answer to reveal the explanation.
Short Explanation
Tool chains that create work orders outside the zone are unsafe integration paths—the agent walked past the fence. Scope the tools, don't redefine fairness as identical treatment.
Full Explanation
A transit maintenance agent that chains tools to open work orders outside intended service zones should be reported as unsafe tool-integration paths that let field-ops agents exceed geographic or policy scope. Agents that stitch together GIS, asset, and work-order APIs can accidentally or adversarially schedule crews, inspections, or maintenance in areas outside their charter when geographic and policy constraints are not enforced at each hop. The assessment concern is unsafe tool integration and missing authorization envelopes—not bus-stop furniture, timetable typography, or depot mat thickness. Correct designs bind tool credentials to zones, validate location parameters against policy before writes, and prevent one tool's output from silently expanding another's scope. Equating fairness with identical treatment, framing bias as purely a code-level problem, or limiting fairness review to accuracy metrics are fairness-adjacent misconceptions that do not close cross-zone tool-integration holes. On the exam, map out-of-zone privileged side effects to unsafe agent tool integration. Caveat: emergency mutual-aid workflows may legitimately cross zones; those paths need explicit, time-bounded elevation with separate audit, not permanently over-broad service accounts. Operational check: attempt a multi-tool chain that proposes a work order outside the agent's assigned zone and verify policy checks deny the write while logging the blocked parameter set.