Static inspection confirms an explicit, package-aligned MCP capability rather than covert execution or exfiltration. The scanner's dynamic-import, environment, network, and remote-dependency signals do not establish malicious behavior.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
User or MCP client invokes the execute tool after starting the CLI.
Impact
Can perform Finch API operations authorized by supplied credentials; no unconsented install-time or foreign-host exfiltration is established.
Mechanism
sandboxed caller-supplied SDK code execution
Evidence
package.jsonsrc/index.tssrc/code-tool.tssrc/code-tool-worker.tssrc/http.tssrc/instructions.ts