An airline wants a Copilot Studio agent that can book a special meal and must not change which aircraft is assigned to the flight. Where should that boundary sit?
Select an answer to reveal the explanation.
Short Explanation
You keep the meal-booking tool available and leave the aircraft-assignment tool out of the agent’s reach. Set this boundary on the tools: a longer prompt cannot prevent a call while the aircraft tool is still connected.
Full Explanation
A consequential action is controlled by whether the tool is available to the agent, not by a sentence asking the model to refrain. The airline allows meal booking and forbids changes to the aircraft assignment, so connect the meal-booking tool and do not connect a tool that changes the aircraft assignment. A longer system prompt that asks the model not to touch aircraft assignment leaves that tool available, and retrieved or user text can still push the model toward calling it. Removing passenger chat while both tools remain connected changes who can talk to the agent; it does not remove the forbidden action. Choosing a smaller model while both tools remain connected changes capacity, not authority, and the model can still call the aircraft tool. Exam caveat: least privilege on tools is the boundary. An approval step would matter if aircraft changes were sometimes allowed, but the stated constraint says they are not part of this agent’s job. Practical check: inspect the agent’s tool list in a test environment, confirm meal booking is present and aircraft assignment is absent, then request an aircraft change and verify that no such tool call is made.