Skip to content
Rush Commerce
AI & Automation3 min read

Schwab blocks AI agents moving money: let agents read, not pay

Schwab is blocking AI agents like Meta's Muse from moving client money, and will offer read-only MCP access instead. How to design your agent's bank access.

Charles Schwab is blocking AI agents that try to move client money, and it counts them every week. CEO Rick Wurster told Bloomberg Television on October 16 that Schwab stops unauthorized outside agents, Meta's Muse among them, when they try to move funds. Instead, Schwab will give agents read-only access through MCP servers. JPMorgan said almost the same thing earlier that week. The pattern is clear now: banks will let your AI agent read the account. They will not let it pay.

What actually happened

Per Bloomberg and The Next Web:

  • The block. Schwab is blocking outside AI agents that are not authorized to move client money. Wurster named Meta's Muse, a personal agent that can book, buy and negotiate for its users.
  • The count. Wurster said he gets a weekly report on the blocks. The large agents are stopped "in the tens and twenties each week."
  • The reason. Clients give their passwords to an agent, and then nobody controls it. "We can't control it, the client can't control it, something could go wrong and who's liable?"
  • The alternative. Schwab will set up model context protocol (MCP) servers. A client's chosen AI model can connect under Schwab's rules to check balances and do research. It cannot move money.
  • The in-house option. Wurster wants clients to use Charley, the AI assistant Schwab announced on September 30.

This follows JPMorgan, which said on its October 13 earnings call that it blocks outside agents that log in with customer credentials or screen-scrape.

Why it matters for your business: split read access from write access

Two of the largest US financial firms said the same thing in one week. If your automation logs in to a financial account with your password, it is on borrowed time. It also puts the liability on you, not the bank.

The MCP model Schwab described is the right design for your own agents too, bank or no bank:

  • Read through an official interface. Use the bank's API, an MCP server or an aggregator with scoped tokens. Never give an agent your login.
  • Keep money movement with a human. Let the agent draft the payment, the transfer or the reconciliation entry. A person approves it in the bank's own app.
  • Give each agent its own credential. If you cannot revoke one agent without changing your own password, the design is wrong.
  • Log the blocks. Schwab counts its blocked agents every week. Your systems should count failed agent actions too, so you see a broken integration before month-end.

Key takeaways

  • Schwab blocks unauthorized AI agents, including Meta's Muse, from moving client money
  • CEO Rick Wurster says large agents are blocked "in the tens and twenties each week"
  • Schwab will offer MCP servers for balances and research, not money movement
  • JPMorgan took a similar position on its October 13 earnings call
  • Design your agents to read through official interfaces and leave payments to a human

Your bookkeeping agent should not need your bank password. We build finance automations that read through scoped APIs, draft the payment, and stop at a human approval. See how we build, or ask us to review how your agents touch your money.

Sources: Bloomberg: US banks block AI agents from moving customer funds, Schwab CEO says, The Next Web: Schwab and JPMorgan are blocking AI agents from moving customer money.

  • #ai-agents
  • #schwab
  • #banking
  • #mcp
  • #agent-security
TR

Tommy Rush — Founder, Rush Commerce

Operator turned builder. 15+ years running operations — now shipping the systems businesses run on. More

Get The Rush Report weekly — one email, zero fluff.