Your execution environment
Your agent continues running on infrastructure you operate. Reporting uses outbound HTTPS; no inbound port or model-provider key is required for the supervision integration.
SECURITY & TRUST
Know what you are trusting. And where it stops.
Understand Toolcaise’s outbound integration, scoped credentials, human review, and the limits of cooperative agent controls.
01Your agents
Local · cloud · scheduled
02Toolcaise
Activity · incidents · outcomes
03Your decision
Review · approve · investigate
04Your runner
Handle the decision at a checkpoint
Scoped access
Register an agent in your workspace and use an agent-scoped credential for reporting. Keep credentials in secure runner configuration and revoke compromised credentials. Account and workspace access remain separate from the runner’s reporting identity.
Metadata you choose to report
Send the operational information needed for supervision: run state, step context, timing, and optional usage or outcome details. Do not put secrets, raw prompts, or unnecessary personal information into telemetry fields.
Human decisions with explicit limits
Review and approval records are separate from agent-reported execution. Guarded actions bind authorization to an action digest and consume it once. Cooperative controls require compatible checkpoints.
Security questions deserve specific answers
Do not infer a compliance certification, contractual SLA, guaranteed data residency, or regulatory suitability from this page. Discuss your requirements and the applicable agreement before sending regulated or sensitive data.
START WITH ONE WORKFLOW
Put your next run
under supervision.
Connect the agent you already run. Build confidence from the work you can actually review.