Spend Controls for Anthropic Claude Agents

Claude Code, Claude Agent SDK, and Anthropic-powered agents can call tools that spend money — provisioning cloud resources, calling paid APIs, triggering Stripe charges. sipi.bot is a native MCP tool they call before any payment, returning approve, block, or flag in under 5ms.

Native MCP integration. sipi.bot ships a Model Context Protocol server that Claude Code, Cursor, and Hermes load directly as a tool. Your agent evaluates every proposed spend through the MCP tool before executing the payment action — no HTTP plumbing required.
# install
pip install sipi-bot
# run the MCP server (stdio)
python -m spendfirewall.mcp_server

Why Claude agents need spend controls

Claude agents are particularly capable tool-users — they can chain tools, write and execute code, and call shell commands. That capability cuts both ways: a Claude Code agent that can run aws ec2 run-instances or call a paid data API can spend real money, fast. The failure modes that matter:

The three-decision model

sipi.bot returns one of three decisions for every proposed spend, in under 5ms:

The FLAG path is what makes sipi.bot usable in production. A binary cap either blocks too much (breaking the agent's workflow) or allows too much (the $12,400 morning). Flagging routes the ambiguous cases — a $500 compute buy at 3am from a vendor you've used before — to a human without blocking the routine ones.

Rules that matter for Claude agents

Velocity limit

Claude's tendency to retry failed tools means velocity is your most important rule. Cap the number of transactions per hour and the retry loop dies on the Nth attempt.

{"rule_type": "velocity", "params": {"max_count": 10, "window_minutes": 60}, "action": "BLOCKED"}

Time windows

Most runaway Claude Code incidents happen during unattended overnight sessions. Flag or block all agent spend outside business hours.

{"rule_type": "time_window", "params": {"allowed_hours": "9-18"}, "action": "FLAGGED"}

Merchant allowlist

Block spend at any vendor you haven't explicitly approved — your defense against prompt-injection-driven spend and novel-vendor discovery.

{"rule_type": "merchant_allow", "params": {"allowed": ["anthropic.com", "aws.amazon.com", "stripe.com"]}, "action": "BLOCKED"}

Anthropic rate limits vs sipi.bot

Anthropic rate limitssipi.bot
What it limitsCalls to the Anthropic APIAny payment the agent triggers
DirectionInbound (you paying Anthropic)Outbound (agent spending your money)
Per-merchantAnthropic onlyAny merchant / vendor / API
Velocity killNoYes
Human approval queueNoYes
Audit logUsage dashboardsTamper-evident, compliance-grade
Add sipi.bot to your Claude agent →