inspect_wasm_artifact on ledger.wasm
Top row: two entry points, the CLI command rea inspect-wasm-artifact and the MCP call tools/call inspect_wasm_artifact. Both reach the wabt-artifact provider, which reads REA_WABT_BIN_DIRECTORY=/opt/homebrew/bin and copies ledger.wasm, 290 bytes, SHA-256 699f6ff7, to a read-only module.wasm in a private workspace. Third row: three WABT 1.0.42 programs run on the copy, wasm-validate --enable-all, wasm-objdump -h -x, and wasm2wat --enable-all. Bottom: one Evidence record ev_3a09e4b0, observed, with validation valid, seven sections, an interface of one import and five exports, the decoded WAT with SHA-256 37eab56a, a tool profile, and five limitations. runtime_execution and network_fetch are not-performed. The CLI prints the record, and MCP returns the same record as structuredContent with the untrusted-content marker.
rea inspect-wasm-artifact
CLI, exit 0 after 1.5 s
tools/call inspect_wasm_artifact
MCP step 24, ok after 404 ms
wabt-artifact provider, REA_WABT_BIN_DIRECTORY=/opt/homebrew/bin
copies ledger.wasm, 290 bytes, sha256 699f6ff7, to a read-only module.wasm
path
path
wasm-validate
--enable-all, banner 1.0.42
result: valid
wasm-objdump
-h -x, banner 1.0.42
result: 7 sections
wasm2wat
--enable-all, banner 1.0.42
result: decoded WAT
Evidence ev_3a09e4b0, confidence observed
sections: Type, Import, Function, Memory, Export, Code, Data
interface: 1 import env.log, 5 exports with typed signatures
wat: decoded-wat, sha256 37eab56a, tool_profile: 3 commands
limitations: 5, runtime_execution and network_fetch not-performed
The CLI prints this record. MCP returns the same id as structuredContent.