Get available statements for an account.
AI agents call chase_statements 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 financial statements, which is a read operation with no side effects or data modification. However, severity is high rather than low because statements contain sensitive personal financial information (account details, transaction history, balances) that could be misused if an AI agent retrieves them without proper authorization context or shares them inappropriately.
From the tool's definition Tool name 'chase_statements' and description 'Get available statements for an account' indicate a retrieval operation. The server description emphasizes 'read-only interface' and 'view balances, transactions, statements'.
Attacks that exploit this kind of access
Get available statements for an account. 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_statements: 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_statements 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_statements 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_statements. 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_statements 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 →