Design guardrails for an agent that can search docs and update tickets.

Instruction: Explain the safety controls you would put around an agent that mixes read and write actions.

Context: Assesses whether the candidate can design a practical architecture and explain the main tradeoffs. Explain the safety controls you would put around an agent that mixes read and write actions.

Official answer available

Preview the opening of the answer, then unlock the full walkthrough.

I would separate read privileges from write privileges and make ticket updates policy-aware. Searching docs is a lower-risk action than mutating a ticket that may trigger downstream workflow, customer communication, or SLA handling.

The guardrails should include permission checks, schema validation for updates, allowed field constraints, evidence...

Related Questions