Build and publish an AI agent

Define the agent boundary

Give an agent a clear business purpose, allowed facts, required questions, prohibited claims, escalation conditions and enabled tools. A narrow specialist is easier to validate than one prompt that tries to control every workflow.

Use versions and validation

1. Edit a draft workflow or create from a suitable tenant-safe template.
2. Connect only required knowledge and tools.
3. Validate the workflow and resolve blocking findings.
4. Test representative and adversarial requests in the playground.
5. Publish the approved version and record the change.
6. Pause or roll back when production results regress.

Treat tools as business actions

A tool that creates an order, sends a message, checks payment or opens a ticket must enforce the active tenant and validate its inputs. The prompt should never be the only authorization boundary.