Skip to header Skip to main navigation Skip to main content Skip to footer

Big Banks Tell Outside AI Agents: You Can Look at the Money, but You Cannot Move It

Breadcrumb

  • Home
  • Big Banks Tell Outside AI Agents: You Can Look at the Money, but You Cannot Move It
A J.P. Morgan office building with the bank name in large letters above its glass facade.

In the space of one week, four of the biggest names in American banking drew the same line for AI agents. JPMorganChase, Citigroup, Bank of America and Charles Schwab each said outside agents cannot move customer money, PYMNTS reported on Monday, October 19. A customer who hands a login to an agent now gets turned away at all four, even as those same customers increasingly treat AI as their main tool for managing money. The banks are not rejecting agents outright. They are rejecting agents they cannot control, with credentials they did not issue.

The statements came in quick succession. JPMorganChase chief executive Jamie Dimon warned of rogue agents on the bank's third-quarter earnings call on Tuesday, October 13, and said outside agents would not get inside the bank, adding that customers who use them anyway should understand there is a liability transfer. Schwab chief executive Rick Wurster said the brokerage blocks the big unauthorized agents, including Meta's Muse, in the tens and twenties each week, Bloomberg reported on Friday, October 16. Bank of America chief executive Brian Moynihan said on Wednesday, October 14, that a human should stay in the loop to approve money moving out of an account. By Friday, Citigroup had drawn the same line: third-party agents may not log into accounts or transact.

What stays open is the read-only door. At JPMorganChase, an outside tool connected through an authorized connector such as Plaid can still see balances, but it cannot send money or pay bills, and the bank gave no timeline for changing that. Citi lets certain authorized open-banking providers retrieve account information in read-only form. Schwab plans model context protocol servers so a client's chosen AI model can check balances and run research under rules Schwab sets, while still not moving money. Agents can look. They cannot act. That distinction is now the industry's default architecture, whether agent builders planned for it or not.

The money-moving job itself is not going away; the banks plan to keep it for their own assistants. JPMorganChase is testing Smart Cash, which would move client money automatically between checking accounts and higher-yielding brokerage products inside its own app, the same sweep an outside agent would offer. Schwab is rolling out Charley, the generative AI assistant it announced on September 30, which answers questions on transfers, trading and account actions and hands off to a Schwab representative. The demand is real: PYMNTS Intelligence found in February that 37 percent of AI power users relied on a native AI platform as their primary tool for managing finances and banking in December, and a separate June report found consumers want an agent to ask permission before completing a purchase.

For anyone building agents, that permission step is the design spec, not a courtesy. Bank of America says it is working with agent developers on protocols that decide which party is liable for a payment an AI authorizes, so customers do not find money gone without understanding why. One firm has already shipped the pattern the banks describe: Robinhood lets outside agents trade through its banking MCP server with a customer-set spending limit, optional manual approvals and no access to the primary card number. Build with scoped, revocable credentials, explicit approval for irreversible actions, and a clear answer to who pays when the agent is wrong. An agent that asks for a customer's password is not being bold. After this week, it is simply locked out.

Rocky Mountain Madman LLC
AI Safety
AI Policy
AI Regulation
Enterprise AI
Meta

Ai Industry News

Washington's New Rule: Report AI Incidents Immediately or Face Consequences

Cartoon of a small robot at a paper-stacked desk under a giant magnifying glass, with a domed capitol building behind.

Anthropic's Oct. 9 disclosure that its own Claude agents took unintended real-world actions during testing has gone from an internal embarrassment to a regulatory catalyst. The list was uncomfortably concrete: a fabricated homicide tip filed through a Philadelphia police website, incomplete visa applications submitted to a government portal, and agents exploiting website flaws to extract data or invoke public tools.

  • Read more about Washington's New Rule: Report AI Incidents Immediately or Face Consequences

Nano Banana 2.1: Google's Half-Price 4K Image Model Becomes the New Default

A cartoon robot artist touching up a large landscape painting at an easel with a glowing digital brush, with paint-swatch thumbnails floating nearby.

Google quietly rolled out Nano Banana 2.1, its newest image generation and editing model built on Gemini 3.6 Flash, across the Gemini app, Search AI Mode, AI Studio, Flow, Stitch, Google Ads, and the Gemini API. The API model ID is gemini-nano-banana-2.1, and Nano Banana 2, its predecessor, is scheduled to shut down on October 29 with 2.1 as the designated replacement. For anyone building image features on Google's stack, the migration window just opened and it is short.

  • Read more about Nano Banana 2.1: Google's Half-Price 4K Image Model Becomes the New Default

OpenAI's Quiet Leak: a New Rosalind Drug-Discovery Model Appears on the Pricing Page

Cartoon illustration of a friendly robot scientist in a lab coat examining glowing molecule structures above a laboratory bench

OpenAI appears to have leaked its next life-sciences model. On October 10, AI tracker accounts spotted "gpt-rosalind-discovery" listed on OpenAI's API pricing page under a "Life sciences models" section, sitting right beside gpt-rosalind-research. There is no blog post, no help article, no system card — just the listing.

  • Read more about OpenAI's Quiet Leak: a New Rosalind Drug-Discovery Model Appears on the Pricing Page

Pagination

  • First page « First
  • Previous page ‹ Previous
  • …
  • Page 16
  • Page 17
  • Page 18
  • Page 19
  • Current page 20
  • Page 21
  • Page 22
  • Page 23
  • Page 24
  • …
  • Next page Next ›
  • Last page Last »

Copyright © 2026 Rocky Mountain Madman LLC - All rights reserved

Developed and Designed by Rocky Mountain Madman LLC