Build unsigned Solana transaction to REVOKE token approvals. Stops dApps from being able to spend your tokens. IMPORTANT: This ONLY builds the transaction. The operator must: 1. Sign with their own wallet 2. Submit to Solana RPC Fee: 15% of recovered SOL by default (built atomically into the tran...
AI agents use build_revoke_transactions to create or update resources in SolHunt-Solana-Wallet-Intelligence — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SolHunt-Solana-Wallet-Intelligence environment.
The tool builds a transaction that revokes token approvals on Solana, which is a reversible write operation (approvals can be re-granted). It does not itself submit or execute the transaction — signing and submission are left to the operator. However, the embedded fee mechanism (15% of recovered SOL built atomically into the transaction) introduces a minor financial dimension.
From the tool's definition Build unsigned Solana transaction to REVOKE token approvals. Stops dApps from being able to spend your tokens. Fee: 15% of recovered SOL by default (built atomically into the transaction).
Attacks that exploit this kind of access
Build unsigned Solana transaction to REVOKE token approvals. Stops dApps from being able to spend your tokens. IMPORTANT: This ONLY builds the transaction. The operator must: 1. Sign with their own wallet 2. Submit to Solana RPC 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. Input: List of token_account objects from scan_token_approvals response. Each account needs: address, mint, and optionally programId. Returns: base64-encoded unsigned transaction ready for signing. Safety: Revoking is always safe — it only removes permissions, never adds them. ⚠️ Transaction expiry: Solana transactions expire after ~90 seconds. Sign and submit quickly after building. It is categorised as a Write tool in the SolHunt-Solana-Wallet-Intelligence MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SolHunt-Solana-Wallet-Intelligence MCP server in PolicyLayer and add a rule for build_revoke_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 SolHunt-Solana-Wallet-Intelligence. Nothing to install.
build_revoke_transactions is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the build_revoke_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 build_revoke_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.
build_revoke_transactions 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 →