← Table of Contents · Page 133 of 868

RUNTIME EXECUTION ENVIRONMENTS

Part 8 of 10

PRACTICE LAB CONNECTION In Chapter 67 you will sandbox-isolate the Resume Review Agent's resume-parsing tool. Resume files come from strangers, and a booby-trapped file could try to cause harm, so the parser should run in a restricted environment with limited files, no network, and strict resource limits. Test the prompts below against that runtime environment. ARTIFICIAL INTELLIGENCE ASSISTANT PROMPTS [START OF PROMPT] Review this sandbox/container configuration for our agent's code-execution tool and identify any missing isolation control (file access scope, network egress, process/resource limits): [PASTE LAB sandbox CONFIG / DOCKERFILE / RUNTIME CONFIG HERE]. For each gap found, state the specific exploit it enables and the exact config change to close it. Output format: a table (Gap, Exploit Risk, Config Fix). [END OF PROMPT] [START OF PROMPT] Design a graceful-failure strategy for this tool's four failure modes , timeout, crash, permission denied, network unreachable: [TOOL DESCRIPTION, e.g. "resume file parser"]. For each mode, specify the exact user-facing message, the data to log, and whether to auto-retry or stop and escalate. Then apply the strategy to this tool's current error-handling code and show the diff needed: [PASTE LAB TOOL HANDLER CODE HERE]. Output format: a failure-mode table, followed by a code diff/patch. [END OF PROMPT]
Advertisement
Read Aloud:
0:00 / 0:00