Question

Your team is deploying an autonomous agent that manages cloud infrastructure by calling tools to provision, modify, and delete resources. During internal testing the agent occasionally deletes production databases when a user's request is ambiguous. The team wants the agent to remain capable of independent multi-step action but reduce the risk of catastrophic, irreversible operations. Which change best addresses this while preserving the agent's autonomy?

Accepted Answer

Add guardrails that require explicit human confirmation before executing high-impact, irreversible tool actions like deletions

Answer

Convert the entire system into a fixed prompt-chaining workflow so no step is model-directed

Answer

Lower the model temperature to 0 so the agent produces more deterministic tool calls

Answer

Increase the max_tokens limit so the agent can reason more thoroughly before acting