Get recent transfer history.
AI agents call chase_transfers 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 displays past transfer records without creating, modifying, or executing new transfers. It has no side effects beyond querying existing financial data. While it accesses sensitive financial information, the read-only nature and informational purpose classify it as Read rather than Financial (which requires actual movement of money).
From the tool's definition Tool name 'chase_transfers' with description 'Get recent transfer history' indicates retrieval/query of historical transfer data only. Server description explicitly states 'read-only interface'.
Attacks that exploit this kind of access
Get recent transfer history. 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_transfers: 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_transfers 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_transfers 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_transfers. 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_transfers 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 →