Get transaction history for a Solana wallet address
AI agents call get_transaction_history to retrieve information from Solafon MCP 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 from a blockchain without side effects. It does not execute transactions, modify state, delete data, or commit financial obligations. While it may expose financial information (transaction details), the tool itself is a read-only query operation with minimal risk if misused — an AI agent could only retrieve data it is already authorized to access.
From the tool's definition Tool name is 'get_transaction_history' and description states it 'Get transaction history for a Solana wallet address' — a pure retrieval operation with no modification or execution of actions.
Attacks that exploit this kind of access
Get transaction history for a Solana wallet address. It is categorised as a Read tool in the Solafon MCP MCP Server, which means it retrieves data without modifying state.
Register the Solafon 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 Solafon MCP. 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 Solafon MCP server (solafon/solafon-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 →