Financial Circuit Breaker ​

Automatically halts all AI agent traffic when request rates exceed your budget ceiling. Requires human approval to resume. No exceptions.

When AI agents operate autonomously, a single misconfigured prompt or recursive tool chain can generate thousands of API requests in minutes. The Financial Circuit Breaker monitors request velocity across your entire account and trips the moment your defined threshold is exceeded — immediately blocking all further tool calls until a human explicitly approves resumption.

This is not a soft rate limit. It is a hard stop with a human-in-the-loop gate.

Instant
TRIP ON THRESHOLD
Human
APPROVAL TO RESUME
Global
ACCOUNT-WIDE PROTECTION
CIRCUIT BREAKER
Budget exceeded. Traffic halted.
Awaiting your approval.
AI agents don't have budgets. You do. The circuit breaker enforces your financial boundaries at the infrastructure layer — the agent cannot negotiate, bypass, or ignore it.

Why this matters now ​

AI agents are becoming more autonomous. They chain tool calls, retry on failure, and explore APIs without human supervision. A single recursive loop can turn a $5/month API bill into a $500 surprise overnight. Traditional rate limiting doesn't solve this — it slows requests down but never stops them entirely:

RECURSIVE TOOL CHAINS
An AI agent calling a list endpoint, then calling a detail endpoint for each item, then calling related endpoints for each detail — can generate thousands of sequential requests from a single user prompt. Each request consumes tokens and API quota.
RETRY AMPLIFICATION
When a tool call fails, many AI clients automatically retry — sometimes with increasingly aggressive strategies. A temporary 500 error can trigger dozens of retries per second, each consuming your request quota. Without a hard stop, retries alone can exhaust your budget.
MULTI-AGENT STACKING
Multiple AI clients connected to the same account can independently generate high request volumes. Without account-level protection, the combined throughput of several agents can exceed any single-server rate limit.
OVERNIGHT SPENDING
Autonomous agents don't stop at 6 PM. A scheduled agent running overnight with a misconfigured loop can exhaust your monthly quota before you wake up — turning controllable costs into unrecoverable overages.

How it works ​

TRIP SEQUENCE
01AI agents make MCP requests across your servers
02Each request is counted in a sliding time window (configurable, 1–60 minutes)
03Request count exceeds your configured threshold — breaker trips
04All subsequent tool calls return 429 Too Many Requests
05Dashboard shows Circuit Breaker Tripped alert with resumption controls
06Human clicks Approve Resumption — or waits for auto-reset after cooldown

The breaker operates at the infrastructure layer. It cannot be bypassed, negotiated, or ignored by the AI agent — the proxy simply stops forwarding requests.

Configuration ​

The circuit breaker is controlled from Settings → Circuit Breaker in the Vinkius Cloud dashboard. All parameters apply globally across your account.

MAX REQUESTS
Request Threshold
Maximum number of MCP requests allowed within the detection window before the breaker trips. Configurable from 100 to 50,000 requests. Default: 5,000.
Slider control with real-time value display
DETECTION WINDOW
Time Window
Sliding time window in minutes used to count requests. Shorter windows detect spikes faster but may trigger on normal bursts. Configurable from 1 to 60 minutes. Default: 5 minutes.
Shorter = faster detection, higher sensitivity
COOLDOWN PERIOD
Auto-Reset Timer
Duration in minutes the circuit stays open before automatically resetting. If you don't manually approve resumption within this period, traffic resumes automatically. Configurable from 1 to 60 minutes. Default: 15 minutes.
MASTER TOGGLE
Enable / Disable
The circuit breaker can be toggled on or off globally. When disabled, no request counting or threshold enforcement occurs. Enabled by default on all accounts.

Using the Circuit Breaker from the Dashboard ​

The circuit breaker is managed entirely from the Vinkius Cloud dashboard. Here's how to configure and monitor it:

Setting up ​

SETUP STEPS
01Navigate to Settings → Circuit Breaker in the sidebar
02Make sure the master toggle is enabled (on by default)
03Adjust the Max Requests slider — this is the total number of requests allowed within the detection window before tripping (100–50,000)
04Set the Detection Window — the sliding time window in minutes to count requests (1–60 min)
05Set the Cooldown Period — how long traffic remains halted before auto-resetting (1–60 min)
06Click Save Settings — changes take effect immediately across all servers

Responding to a trip ​

When the circuit breaker trips, a prominent amber alert appears at the top of the Circuit Breaker settings panel:

⚠️
Circuit Breaker Tripped
Agent traffic is currently halted. Your budget is protected. Approve resumption when ready.
↻ Approve Resumption

You have two options:

  1. Manual resumption — Click Approve Resumption to immediately restore traffic. Use this when you've identified and resolved the cause of the spike.
  2. Wait for auto-reset — After the cooldown period expires, traffic resumes automatically. Use this when you want the system to self-heal while you investigate.

BEST PRACTICE

After a trip, check the Audit Logs on your server detail pages to identify which tool or agent caused the spike. Common culprits include recursive tool chains, retry loops, and misconfigured polling agents.

Circuit breaker vs. traditional rate limiting ​

The circuit breaker is fundamentally different from per-endpoint rate limiting. Rate limiting throttles individual endpoints — the circuit breaker protects your entire budget:

BEHAVIORRATE LIMITINGCIRCUIT BREAKER
ScopePer endpointEntire account
When triggeredSlows requests downStops all requests
RecoveryAutomatic after delayHuman approval required
Multi-server protectionEach server independentAll servers combined
Budget awarenessNoYes
Prevents runaway loopsPartiallyCompletely

When the breaker trips ​

AI CLIENTS
Every tool call returns 429 Too Many Requests with a Retry-After header indicating when the cooldown expires. Active SSE connections remain open but will not process further tool calls.
DASHBOARD
The Circuit Breaker settings panel shows a prominent alert with the tripped status. An Approve Resumption button allows you to manually reset the breaker and restore traffic immediately.
AUTO-RESET
After the configured cooldown period expires (default: 15 minutes), the breaker resets automatically and traffic resumes. This ensures that a tripped breaker never blocks traffic permanently if the human operator is unavailable.

Real-world examples ​

Concrete scenarios where the circuit breaker protects you — and the recommended settings for each.

SCENARIO 1
Recursive tool chain in Cursor
A developer asks Cursor to "list all users and update each profile photo." The agent calls GET /users (returns 2,000 users), then loops PATCH /users/{id}/avatar for every single one. That's 2,001 requests in under 60 seconds from a single prompt.
WITHOUT CIRCUIT BREAKER
All 2,001 requests execute. Consumes 40% of your monthly quota in one minute. If the agent retries on failures, it can double.
WITH CIRCUIT BREAKER
After 500 requests (your threshold), all further calls return 429. You receive an alert, approve resumption after reviewing, and only 10% of your quota was used.
RECOMMENDED → 500 requests / 2 min window / 5 min cooldown
SCENARIO 2
Overnight polling agent
A scheduled agent monitors a CRM API every 30 seconds, calling GET /deals?status=open to check for new opportunities. At 2 AM, a misconfigured retry policy starts calling the endpoint 10 times per second instead. By morning, it has made 288,000 requests. Your monthly quota is gone.
WITHOUT CIRCUIT BREAKER
288k requests execute overnight. Monthly quota exhausted. Overage charges accumulate. You discover the problem at 9 AM when nothing works.
WITH CIRCUIT BREAKER
After 5,000 requests in 5 minutes, the breaker trips. Traffic halts instantly. At 9 AM, you see the alert, fix the retry policy, and approve resumption. Only 5,000 requests consumed.
RECOMMENDED → 5,000 requests / 5 min window / 30 min cooldown
SCENARIO 3
Multi-agent team sharing an account
A team of 8 developers, each connected via Cursor, Claude Desktop, or Antigravity. During a sprint, several agents are actively calling tools in parallel. Normal combined throughput: ~200 requests/minute. One developer accidentally triggers an agent loop that spikes to 3,000 requests/minute.
WITHOUT CIRCUIT BREAKER
The runaway agent from one developer burns through the shared quota. All 8 team members hit quota limits within hours. Entire team is blocked.
WITH CIRCUIT BREAKER
Breaker trips after 15,000 requests in 10 minutes. Brief interruption for all agents (minutes, not hours). Team lead approves resumption after the offending agent is stopped. Minimal quota impact.
RECOMMENDED → 15,000 requests / 10 min window / 15 min cooldown

Quick reference ​

PROFILEMAX REQUESTSWINDOWCOOLDOWNBEST FOR
Solo developer5002 min5 minTesting, prompt iteration
Small team5,0005 min15 minProduction with 2–5 agents
Growing team15,00010 min15 min6–15 devs, mixed clients
High-throughput30,00015 min30 minHeavy automation, CI/CD

START WITH THE DEFAULTS

If unsure, keep the defaults — 5,000 requests / 5 min window / 15 min cooldown. This configuration catches runaway behavior within seconds while allowing normal production workflows. You can always adjust after observing your actual traffic patterns in the Audit Logs.

Next steps ​

Frequently Asked Questions ​

What is the Financial Circuit Breaker? ​

The Financial Circuit Breaker automatically halts all AI agent traffic when request rates exceed your defined budget ceiling within a configurable time window. It requires explicit human approval to resume — preventing runaway AI agents from generating unexpected costs.

How does the circuit breaker detect runaway behavior? ​

A sliding time window tracks the number of MCP requests across all your servers. When the count exceeds your configured max_requests threshold within the window, the breaker trips instantly. All subsequent requests receive a 429 response until a human approves resumption.

Can the circuit breaker reset automatically? ​

Yes. After the configured cooldown period expires, the circuit breaker resets automatically and traffic resumes. You can also manually approve resumption at any time from the dashboard.

Does the circuit breaker apply per-server or globally? ​

The circuit breaker applies globally across all servers on your account. This ensures that runaway behavior on any single server cannot exhaust your overall budget.

What happens to active AI sessions when the breaker trips? ​

Active SSE connections remain open but all tool call requests return a 429 Too Many Requests response with a Retry-After header. The AI client receives an error message explaining that the budget ceiling has been reached.

Can I configure different thresholds for different servers? ​

Currently, the circuit breaker operates at the account level with a single set of thresholds. This prevents runaway behavior on any server from bypassing budget controls by spreading requests across multiple servers.