Sign and broadcast a transaction with a Solana wallet.
AI agents use solana_signAndSendTransaction to commit financial operations through Privy MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool signs and broadcasts Solana blockchain transactions, which irreversibly moves funds or executes on-chain operations. Broadcasting a transaction to the Solana network cannot be undone, and misuse could result in financial loss. Financial > Destructive in severity hierarchy, as blockchain transactions typically involve asset transfers or commitments.
From the tool's definition Sign and broadcast a transaction with a Solana wallet
Attacks that exploit this kind of access
Sign and broadcast a transaction with a Solana wallet. It is categorised as a Financial tool in the Privy MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Privy MCP Server MCP server in PolicyLayer and add a rule for solana_signAndSendTransaction: 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 Privy MCP Server. Nothing to install.
solana_signAndSendTransaction is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the solana_signAndSendTransaction 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 solana_signAndSendTransaction. 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.
solana_signAndSendTransaction is provided by the Privy MCP Server MCP server (privy-io/privy-mcp-server). 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 →