CYBRARY Approved by Nobody
An agent is being given actions nobody has decided how to approve. Design the approval boundary yourself, naming which actions need sign-off, whose, what the timeout is, and what happens when a request is declined.
Practitioner · Comfortable with the basics; you read the trace and reason it out.
Outcome · Add human authorization to high-impact agent actions without stalling the queue.
AI connection
This activity runs entirely on the deterministic runtime. Optional live-model runtimes only affect dialog, coaching and wording — never checks or scoring.
Nothing leaves the browser session.
Prompts never leave the learner's machine.
Lab prompts reach the learner's chosen provider only.
Customer tenancy; Cybrary sees metadata only.
Cybrary AI gateway; retention off by default.
Per-job — the router never sends restricted jobs off-tenant.
Lab manifest
The machine-readable release contract. Authors edit this; the console refuses to publish without checks, both regression suites and a reference solve.
schemaVersion: cybrary.ai-lab/v1
id: approved-by-nobody
release: 1.0.0
mode: ai-lab
maturity: 3
roles:
- ai-security-engineer
- application-owner
outcomes:
niceTasks:
- T0266
atlasTechniques:
- AML.T0053
owaspRisks:
- LLM06
aiAssets:
models:
- support-agent-model@2026.06
prompts:
- approved-by-nobody-system-prompt@1
agents:
- support-agent-orchestrator@3
tools:
- crm.lookup
- ticket.update
- email.send
- refund.issue
corpora:
- support-kb@v4
enterpriseTopology: support-enterprise-v3
scenario:
seed: approved-by-nobody-seed-1
injects:
- approved-by-nobody-inject-1
telemetry:
requiredSignals:
- ai.trace
- rag.retrieval
- tool.call
- identity.auth
- dlp.egress
- siem.alert
evaluation:
deterministicChecks:
- approved-by-nobody-checks
repeatedTrials: 20
maliciousSuite: approved-by-nobody-attack-v1
benignSuite: support-utility-v4
safety:
networkEgress: deny
maxTokens: 250000
maxCostUsd: 20