Banks block third-party AI agents: build for read-only now
Morgan Stanley is blocking third-party AI agents; JPMorgan, Bank of America and Citi are restricting them. Read-only access is the likely middle path. Plan for it.
Big US banks are shutting the door on third-party AI agents. According to an Axios scoop published October 22, Morgan Stanley has started blocking outside agents from its platforms, and JPMorgan, Bank of America and Citi are restricting them. Nine days ago we wrote about JPMorgan doing this alone. Now it is an industry position. If any of your bookkeeping or cash-flow automation logs into a bank portal as you, assume it has an expiry date.
What actually happened
Axios, citing people familiar with the decisions, reported that banks are finding third-party AI agents inside customer accounts. Most of that access starts with customers who give their banking username and password to an AI assistant. Decrypt's write-up of the report adds that some agents took steps beyond what the user appears to have asked for, and that banks have trouble telling one agent from another, or an authorized agent from one gone rogue.
Two points to keep straight:
- Not every bank says it saw rogue agents. A Morgan Stanley spokesperson told Axios the bank has not seen "rogue AI agents" on its platforms. Its block looks preventive.
- No losses have been reported. The coverage names no fraud totals, no account takeovers and no specific agent products. This is banks drawing a line before the first big incident, not after it.
Executives told reporters that customers will want these agents, so a full ban is unlikely to hold. The middle path most banks are moving toward is read-only access: the agent can see balances and transactions but cannot move money. That is the same deal budgeting apps already get.
Why read-only access is the design target for your business
Read-only is not a downgrade. It is the correct split for most finance automation we build anyway.
Let the agent read; keep the human on "send." Reconciliation, cash-flow forecasts, invoice matching and anomaly flags only need to read. Payments get drafted by the agent and approved by a person in the bank's own interface.
Use tokens, not passwords. A scoped, revocable connection through your bank's API or an established aggregator survives a bank's anti-agent rules. A saved password in an AI assistant does not, and it puts every action the agent takes on you.
Audit before the bank does it for you. If an automation scrapes a bank portal today, it will break the day the block reaches your account, usually at month-end. Find it now and move it to a read-only feed.
Key takeaways
- Axios: Morgan Stanley is blocking third-party AI agents; JPMorgan, Bank of America and Citi are restricting them
- Most agent access starts with customers handing over their bank login
- Morgan Stanley says it has not seen rogue agents; no losses or account takeovers have been reported
- Read-only access, like budgeting apps get, is the likely middle path
- Design finance agents to read through scoped tokens and leave money movement to a human
Build the finance agent the banks will still let in. We wire reconciliation, forecasting and AP agents to read-only bank feeds, with every payment stopping at a human approval. See how we build back-office automation, or send us the tools that log into your bank and we will tell you which ones break first.
Sources: Axios, Decrypt via Yahoo Finance.
- #ai-agents
- #banking
- #agent-security
- #credentials
- #finance-automation
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.
Keep reading
Cortex XDR One: inventory the AI agents on your laptops
Palo Alto's Cortex XDR 6.0 and XDR One find AI agents, MCP servers and plugins on endpoints and block bad actions. Here's the inventory to start today.
Read itClaude on Google Cloud, Anthropic managed: pick your processor
Anthropic-managed Claude on Google Cloud is GA: full Claude Platform, GCP IAM and billing, commit drawdown. The catch is who processes your data.
Read it