Agent Guardrails and Secure Development
Audit the parser test environment
BOTIE
Examples, experiments and workspace controls
Connect a tool's inputs to see what it produces. You can try a branch before connecting it to Result.
Try your own inputs
Use a copy of the example to try your own data. Keep the problem's assumptions in mind, and predict the effect of a change before checking the output. You can also add another branch to compare two ways of doing the calculation.
Context for this challenge
Compare writable mount paths with the explicitly approved locations.
The offline parser job should have scratch space but no ambient credentials or network.
Inspect the component calculation
Inspect writable mounts( Execution profile: Execution profile Approved writable paths: Approved writable paths )
Examples and results
- Execution profile
{ "mounts": [ { "path": "/scratch", "mode": "rw" } ], "credentials": [], "network": "none", "privileged": false, "timeout": 30 }- Approved writable paths
- 0/scratch
- Required result
[]
- Execution profile
{ "mounts": [ { "path": "/scratch", "mode": "rw" } ], "credentials": [ "cloud-token" ], "network": "none", "privileged": false, "timeout": 30 }- Approved writable paths
- 0/scratch
- Required result
[]
Try a fresh construction
This clears this draft, including its undo history. Earlier successful attempts stay recorded. Build again without opening hints to record an independent attempt.
Stuck? Inspect a worked construction
The tools below form one possible solution. You can assemble it, follow its signals, and undo that change to return to your own construction.
Assumptions and test precision
These are invented records and deterministic policy checks. The browser runs no agent, shell command, MCP server or network request. Passing these fixtures establishes only the stated policy behaviour. Numerical tests allow a difference of 0.001. Lists and structures must also have the right shape.
Your last tested pieces can start the full construction. An existing draft there keeps its own pieces.
A timeout field is present but disables the bound
This check uses the pieces from “Preserve every profile finding”.
BOTIE
- Execution profile
{ "mounts": [], "credentials": [], "network": "none", "privileged": false, "timeout": 0 }- Approved writable paths
[]
Use a number, text, or an array matching the requested result. For a matrix, put each row in brackets. Saving your prediction runs your current construction on these inputs and checks the earlier examples too.
Build a construction in the workspace above first. This case will test those pieces.
How would you prove that the launched worker cannot read an excluded file?
Run disposable probes against the runtime, not just its configuration.
These are invented records and deterministic policy checks. The browser runs no agent, shell command, MCP server or network request. Passing these fixtures establishes only the stated policy behaviour.
Work through the Python challenges →