The inspected source implements user-invoked MCP tools without automatic installation behavior or a concrete malicious chain. Its code execution capability is package-aligned and restricted by Deno permissions.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
The user starts the MCP server and a caller submits a tool request; no install-time attack trigger was identified.
Impact
The tool can perform authorized Conductor API operations; no covert exfiltration, persistence, or agent configuration mutation was identified.
Mechanism
Caller-provided code runs in a Deno worker with restricted network and file permissions using the configured SDK client.