WASI Sandbox Compute Bounds

Problem

An agent may maliciously or accidentally propose a policy or script that contains an infinite loop or massive memory allocation, attempting to exhaust the host's resources (Denial of Service).

Approach

We compile policies to WebAssembly (Wasm) and execute them using Wazero with strict WASI constraints. We inject compute "gas" limits. Every loop or instruction deducts gas. If gas drops to zero, the runtime traps the execution, kills the instance, and yields a DENY_EXHAUSTION receipt.

Invariants

• Memory strictly bounded to 16MB per execution context.
• Maximum instruction limit (gas) enforced at runtime.
• No network sockets available to the guest.

Artifacts

• HELM OSS Reference Kernel

References

• Wazero Runtime Architecture Documentation.