Get past Relay bridge and swap transactions for a wallet address. Returns transaction IDs, statuses, chains, and timestamps. Supports pagination via cursor. Filter by time range, origin/destination chain, or deposit address to narrow results.
AI agents call get_transaction_history to retrieve information from Relay 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 for a wallet address without any capability to modify, delete, execute code, or move funds. It is purely informational and supports standard read operations like filtering and pagination. While it provides visibility into financial transactions, it does not itself execute financial movements or have destructive effects.
From the tool's definition Tool description explicitly states it 'Get[s] past Relay bridge and swap transactions' and 'Returns transaction IDs, statuses, chains, and timestamps.' These are read-only query operations with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get past Relay bridge and swap transactions for a wallet address. Returns transaction IDs, statuses, chains, and timestamps. Supports pagination via cursor. Filter by time range, origin/destination chain, or deposit address to narrow results. It is categorised as a Read tool in the Relay MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Relay MCP Server 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 Relay MCP Server. 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 Relay MCP Server MCP server (relayprotocol/relay-mcp). 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 →