Get all transactions for a wallet with optional filters.
AI agents call get_transaction_history to retrieve information from Tatum 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 transaction history from blockchain networks. It does not execute code, modify state, delete data, or move funds. It simply queries and returns existing blockchain transaction data. The optional filters do not change the read-only nature of the operation.
From the tool's definition Tool name 'get_transaction_history' and description 'Get all transactions for a wallet with optional filters' indicates data retrieval with no modification, deletion, or execution capability.
Documented attack patterns abuse exactly the kind of access get_transaction_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tatum MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_transaction_history:
{
"version": "1",
"default": "deny",
"tools": {
"get_transaction_history": {}
}
} get_transaction_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get all transactions for a wallet with optional filters. It is categorised as a Read tool in the Tatum MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Tatum 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 Tatum 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 Tatum MCP Server MCP server (tatumio/blockchain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Tatum MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 Tatum MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.