Get all Chase accounts - checking, savings, credit cards, investments, and loans.
AI agents call chase_accounts to retrieve information from Chase MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists financial account information but does not create, modify, delete, execute operations, or move money. It is a Read operation with high severity due to the sensitive nature of financial account data exposure—an AI agent with access could enumerate all accounts and expose account types, numbers, and holdings to unauthorized parties.
From the tool's definition Tool description states 'Get all Chase accounts' with no modification or execution capability. The server description emphasizes 'read-only interface' and lists sibling tools including 'chase_balance', 'chase_statements', and 'chase_transactions' which are…
Attacks that exploit this kind of access
Get all Chase accounts - checking, savings, credit cards, investments, and loans. It is categorised as a Read tool in the Chase MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Chase MCP Server MCP server in PolicyLayer and add a rule for chase_accounts: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Chase MCP Server. Nothing to install.
chase_accounts is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the chase_accounts rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for chase_accounts. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
chase_accounts is provided by the Chase MCP Server MCP server (markswendsen-code/mcp-chase). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →