Multi-agent setup triggers $3,400 in charges due to hallucination loop

What happened

A developer building a multi-agent setup using MCP (Model Context Protocol) to automate data scraping and market research encountered a costly failure. The agents were designed to bypass captchas, spin up proxy servers, and pay for gated API access to pull reports.

The technical failure

For testing purposes, the developer hardcoded their standard corporate virtual card into environment variables. They set the script on a cron job on Friday night.

The primary agent got caught in a hallucination loop where it:

• Kept failing a specific captcha on a proxy service
• Assumed the IP was banned
• Spun up a new paid proxy instance to try again
• Repeated this process every 45 seconds for 14 hours

The financial impact

The charges were micro-transactions ($2 to $5 each) to a known cloud provider. The bank's traditional fraud engine didn't flag the activity because it appeared to be legitimate server purchases. The developer woke up on Saturday to over $3,400 in charges.

They managed to get about half refunded after contacting support.

The core problem identified

Standard credit cards and their risk engines are built for human shopping carts, not infinite while loops executing at machine speed. The developer notes that "handing an LLM a traditional Visa is just asking for bankruptcy."

Key questions raised

The developer asks how others are managing spending limits when agents need to buy things to complete tasks.