Get recent transactions for an account.
AI agents call chase_transactions 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 historical transaction data with no ability to modify, delete, or execute actions. While financial data is sensitive, the read-only nature and absence of side effects places it in the Read category. Severity is low because an AI agent misusing this tool can only access information already available to the authenticated account holder, with no financial movement or data modification possible.
From the tool's definition Tool description states 'Get recent transactions for an account' which is a retrieval operation. Server description emphasizes 'read-only interface' and lists capabilities as 'view balances, transactions, statements, and rewards' — all read operations without…
Attacks that exploit this kind of access
Get recent transactions 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_transactions: 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_transactions 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_transactions 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_transactions. 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_transactions 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 →