boomi-runtime

What the scan recorded

Observed events

every tool call, mcp__boomi-runtime__up calls, mcp__boomi-runtime__smoke calls, mcp__boomi-runtime__status calls, mcp__boomi-runtime__logs calls, mcp__boomi-runtime__down calls, mcp__boomi-runtime__doctor calls

Hooks

session.start, tool.call, command.run {command=boomi}, tool.call {tool=mcp__boomi-runtime__up}, tool.call {tool=mcp__boomi-runtime__smoke}, tool.call {tool=mcp__boomi-runtime__status}, tool.call {tool=mcp__boomi-runtime__logs}, tool.call {tool=mcp__boomi-runtime__down}, tool.call {tool=mcp__boomi-runtime__doctor}, session.end, ui.render {component=Pane, requestId=boomi-runtime}

API calls

$.clock.every, $.clock.now, $.clock.sleep, $.command.register, $.env.get, $.fs.exists, $.fs.list, $.fs.read, $.fs.write, $.http.fetch, $.process.run, $.process.spawn, $.session.cwd, $.session.id, $.state.get, $.state.set, $.store.delete, $.store.set, $.tool.register, $.ui.open, $.ui.resolve, $.ui.status, $.ui.toast

Validation on 2.1.302

Passed with warnings

Scanned revision

69a30b05e066

UI rewrite review

UI hook source contains control-character strings. Review any values passed to next() as rewritten props.text; the scanner does not trace whether these strings reach that call. boomi-runtime/hooks/envfile.ts:31

These are the hooks and API calls reported by claude plugin validate. Access levels describe the widest reach of those calls and are not safety ratings. Validation is a static check, not a runtime test, and a passing result does not prove that a mod works or is safe. How the scan works.