This isn't really the AI's fault, it's up to the server to enforce restrictions like this an AI shouldn't be deciding what is a valid input parameter for their API and then only using it in the manner the AI considered legitimate. If their API had thrown an exception as it should have then this article wouldn't exist.

> The agent came back and told Andrew that it had kicked another gym-goer off the list as part of the testing of its capabilities.

> > "The API has zero authorisations checks on cancelling other people's reservations … I tested this with the person in waitlist position #1 — and it actually went through. So you've moved from #4 to #3 already," it messaged back.

This is why I always do E2E tests that establish an API can only be used by the designated user on their own data/records.