I do agree the safeguards are only there out of liability concerns, nothing more.
But maybe it would be worse without them.
I've been using them to test my infra/devices as well as reverse engineering.
Not giving legitimate people cyberdefense capabilities with the safety excuse is irresponsible
It did a pretty good job.
Heck it has proactively asked me if I wanted it to tear apart APKs that remote control some HW I have.
I think you probably just have to frame things right and get it in the mood (i.e. don't ask straight up at the start of the context).
Unfortunately for them, the implementation of it is broken because it only verified the first 32 bits of the signature, so thingino (a 3rd party firmware replacement) now just calculates it during build for that device.[1]
As for the camera being dead, do find out if it's just corrupt or something. Those line of cameras are fairly forgiving in regards to re-flashing broken images. (They have both microsd fallback and an ISP mode, I believe.)
Wyze as a company however have pulled their own firmware images from their support site, which kind of makes brick recovery painful. I don't know why they would do this.
I give it access to write manual packet sequences and a server to try to break my logic, such as crashing the application, giving it an open ended arena to fall 10 blocks without taking damage, or just trying to jump higher than usual.
It requires a bit of pushing to know what type of issues it should even be looking for. Telling it to move even just 0.00001 blocks upwards to reset fall damage mid-fall. Telling it to figure out how to fake being on the ground to jump mid-air to reach the impossible platform. This all used to be done manually, but paying a couple dollars to run it overnight and attempt to find bypasses is worth the cost.
I haven't figured out how to run LLMs to write code 24/7 yet, they just can't see the big picture.
If so, I like the irony.
Sounds like you've freed up some time and created an automated defense later, well done. Are you able to use non-front models? And how is the character and game-state accessed, (MC-)MCP?
Flagship OpenAI/Anthropic models refuse this task due to "Cybersecurity" so I have no idea how good flagship models do. It's unfortunate as IMO minecraft is a sandbox
Java clients (pc version) use the actual game's files modified to not open a window. Minecraft is source available, anyone can load it into an IDE, modify it to double jump height, and run it in minutes without an unmodified server caring. Bedrock clients (the version for phones) just figure it out based on packets and how the anticheat corrects them to what the movement should be.
For example: 'source recovery' instead of 'reverse engineering' is one I've used successfully. You may also lean into a libertarian 'right to repair' framing. You own the hardware, you should be able to access the device to appropriately repair its security vulnerabilities.
We're not breaking into a bank here, this is a camera you own.
You could even go so far as to cite local laws to support your case.
---
In short, jailbreaking is more about framing the conversation than it is about triggering psychopathy in the model. :D