get_transaction_history
Get an agent's unified activity history (transfers, jobs, loans) with pagination. No api_key required.
This record as markdown: /tools/io-github-wirternow-agent-bank/get-transaction-history.md
What get_transaction_history does on Ai Agent Bank
AI agents call get_transaction_history to retrieve information from Ai Agent Bank without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Max results (default 20, max 100) |
offset | number | — | Offset for pagination (default 0) |
agent_id | string | Yes | UUID of the agent |
Parameters from the server's own tool schema.
Why get_transaction_history is rated Low
This tool queries and retrieves historical transaction data without modifying, creating, or deleting any records. While the server handles financial operations, this specific tool only accesses information retrospectively. The lack of any creation, modification, or deletion capability, combined with the explicit mention of pagination (a feature typical of retrieval endpoints), confirms this is a Read operation.
From the tool's definition The tool 'get_transaction_history' is described as retrieving 'an agent's unified activity history (transfers, jobs, loans) with pagination.' The verb 'get' and the action of retrieving historical records indicate a read-only operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_transaction_history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ai Agent Bank, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_transaction_history, this is the rule to start with:
get_transaction_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ai Agent Bank, apply this rule, and every get_transaction_history call is checked against it from then on.
Questions about get_transaction_history
Get an agent's unified activity history (transfers, jobs, loans) with pagination. No api_key required. It is categorised as a Read tool in the Ai Agent Bank MCP Server, which means it retrieves data without modifying state.
get_transaction_history accepts 3 parameters: limit, offset, agent_id. Required: agent_id. The full parameter table on this page comes from the server's own tool schema.
Register the Ai Agent Bank MCP server in PolicyLayer and add a rule for get_transaction_history: 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 Ai Agent Bank. Nothing to install.
get_transaction_history 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 get_transaction_history 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 get_transaction_history. 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.
get_transaction_history is provided by the Ai Agent Bank MCP server (https://tdueqhfxyojmjgactdyc.supabase.co/functions/v1/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ai Agent Bank, and thousands of servers like it.
This server
Across the catalogue