Build unsigned Solana transaction bytes for wallet recovery. Close zero-balance token accounts to recover rent (0.002039 SOL per account). Returns base64-encoded unsigned transaction(s) ready for signing. The operator signs with their own wallet and submits — SolHunt never has custody. Each trans...
AI agents invoke build_recovery_transaction to trigger actions in SolHunt-Solana-Wallet-Intelligence. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes financial operations on a blockchain: it builds transactions that close token accounts, recover rent in SOL, and deduct fees. While the user must sign the transaction, the tool determines what gets executed (closeAccount + fee extraction).
From the tool's definition 'Build unsigned Solana transaction bytes for wallet recovery' and 'Returns base64-encoded unsigned transaction(s) ready for signing' and 'closeAccount instructions' and 'Each transaction includes closeAccount instructions AND a fee to SolHunt built…
Attacks that exploit this kind of access
Build unsigned Solana transaction bytes for wallet recovery. Close zero-balance token accounts to recover rent (0.002039 SOL per account). Returns base64-encoded unsigned transaction(s) ready for signing. The operator signs with their own wallet and submits — SolHunt never has custody. Each transaction includes closeAccount instructions AND a fee to SolHunt built atomically. What you see in get_wallet_report is exactly what gets executed — no surprises. IMPORTANT: Transactions expire after about 90 seconds on Solana. The unsigned transaction needs to be signed and submitted quickly after building! Fee: 15% of recovered SOL by default (built atomically into the transaction). Override with fee_percent (0-100, default: 15). Set to 0 to disable the fee. destination_wallet is the wallet that receives the recovered SOL (can be the same as the source wallet). It is categorised as a Execute tool in the SolHunt-Solana-Wallet-Intelligence MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SolHunt-Solana-Wallet-Intelligence MCP server in PolicyLayer and add a rule for build_recovery_transaction: 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 SolHunt-Solana-Wallet-Intelligence. Nothing to install.
build_recovery_transaction is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the build_recovery_transaction 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 build_recovery_transaction. 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.
build_recovery_transaction is provided by the SolHunt-Solana-Wallet-Intelligence MCP server (shieldspprt/solhunt-recovery). 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 →