Get recent transaction signatures for a Solana address
AI agents call get_recent_transactions to retrieve information from Solana MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries historical transaction data for an address without modifying, executing, or deleting anything. It is a straightforward read operation that retrieves publicly available blockchain data. The low severity reflects minimal blast radius—even if misused by an agent, it only exposes transaction history already visible on-chain.
From the tool's definition Tool name 'get_recent_transactions' and description 'Get recent transaction signatures for a Solana address' indicate a retrieval-only operation with no side effects.
Attacks that exploit this kind of access
Get recent transaction signatures for a Solana address. It is categorised as a Read tool in the Solana MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Solana MCP Server MCP server in PolicyLayer and add a rule for get_recent_transactions: 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 Solana MCP Server. Nothing to install.
get_recent_transactions 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_recent_transactions 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_recent_transactions. 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_recent_transactions is provided by the Solana MCP Server MCP server (visioneth/solana-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 →