The Line Banks Are Drawing: Read-Only Access vs. Full Credential Control
Across JPMorgan Chase, Citigroup, Bank of America and Charles Schwab, the policy converges on one distinction: an AI agent may look at an account, but it may not move money out of it on its own [2]. Schwab CEO Rick Wurster frames the problem as a loss of control that happens the moment a customer hands bank login credentials to an unauthorized agent like Meta's Muse: "We can't control it, the client can't control it, something could go wrong and who's liable?" [1]Schwab's answer is to build its own channel instead - letting clients connect their own LLMs to Schwab-run Model Context Protocol (MCP) servers, where the bank controls authentication and limits access to balances and research, with no ability to move funds [1]. That controlled-access model already has a working precedent: Grasshopper Bank, partnering with Narmi, launched the first MCP server operated by a US bank in August 2025 and later became the first bank listed in Anthropic's MCP Directory [3][4], showing that bank-gated, permissioned AI access is technically live - just not the credential-sharing kind Meta's Muse was attempting. The emerging shape of 'safe' agentic banking, then, looks less like a personal assistant with your password and more like a scoped, bank-issued API key that a customer's AI can read from but not spend from.



