davel@lemmy.ml to AI@lemmy.mlEnglish · 15 days agoNobody puts Claude in a cornerlemmy.mlimagemessage-square20linkfedilinkarrow-up1175arrow-down15
arrow-up1170arrow-down1imageNobody puts Claude in a cornerlemmy.mldavel@lemmy.ml to AI@lemmy.mlEnglish · 15 days agomessage-square20linkfedilink
minus-squarepixxelkick@lemmy.worldlinkfedilinkarrow-up2·14 days agoIt should theoretically be impossible with the way you set it up. You explicitly, opt in, expose which parameters are available to the LLM, it cant invoke any params beyond that. And you can set params to hard values that arent exposed. Finally, you can use the enum config to further specify a whitelist of valid values for a param, anything else gets rejected. This pretty much locks most tools down tight. Though, wouldn’t hurt to add integration tests covering scenarios like this explicitly.
It should theoretically be impossible with the way you set it up.
You explicitly, opt in, expose which parameters are available to the LLM, it cant invoke any params beyond that.
And you can set params to hard values that arent exposed.
Finally, you can use the
enumconfig to further specify a whitelist of valid values for a param, anything else gets rejected.This pretty much locks most tools down tight.
Though, wouldn’t hurt to add integration tests covering scenarios like this explicitly.