ToolApprovalConfig value, declared three different ways.
You’ll end up with. Printed in-memory values, the exact serialized save-payload the backend will receive, and (with a key set) a successful save + delete round-trip.
Verifies that every way of creating a tool accepts approval_config and
that the value flows through to the serialized save payload the backend
consumes.
Paths exercised:
VECTORSHIFT_API_KEY is set,
the example also saves the agent and deletes it to confirm the backend
accepts the payload.
Expected output
approval_config sits at the top of each tool dict (not nested under value or inputs), which is what the backend parser expects.
See also
Session approval respond
Once a tool is gated, this is how the session replies to the pause.
Agent CRUD
Where
save() and delete() come from.Agent reference
Full method surface.
