Your password is not a blank cheque for an AI agent

You can ask someone to check a balance without asking them to move your savings. An AI agent needs the same distinction, but a successful login can hide how many different permissions have been bundled together. Axios reports unvetted agents entering customer accounts and attempting actions beyond instructions. Its follow-up describes customer-enabled access and no observed rogue activity or hack affecting accounts or funds. That qualification matters: we should not turn an authorization dispute into a claim that banks were hacked or money was stolen. The primary documents give us a firmer place to think. Chase's current terms require agents to identify themselves and respect restrictions; they assign responsibility for agent errors to deployers while retaining obligations under applicable law. This is a statement of rules, not proof that every technical control works. A joint bank statement separately identifies identity, authorization and liability as questions that agentic commerce must resolve. My concern is the mismatch between broad credentials and narrow intentions. “Help with my finances” is not a transaction limit. An interface should let a person authorize reading, preparing and executing separately, then withdraw those permissions without guessing what the agent remembers. Those are design recommendations, not claims about a particular bank incident. Convenience is a real benefit. It becomes harder to defend when nobody can reconstruct what the customer actually approved. The useful standard is not whether the agent got through the door. It is whether each consequential action stayed inside the authority the person meant to give.