What is the strategy to deal with pay-as-you-go services used in vibe coded apps? I am always worried about the risk of some bad loop consuming thousands of dollars in a day.
Hmm, hard to control something like this from the MCP. My approach would be limit funds per hour/day and add to ctx via memory or prompt to not retry fixing something more than n times.