Send native SOL from a Chain-Signature-derived Solana address. SAFE: dry=true returns the plan. Amount in lamports (1 SOL = 1,000,000,000 lamports). Requires the derived address to have SOL.
AI agents use hydra_send_solana to commit financial operations through Near Hydra — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool transfers SOL cryptocurrency from a blockchain address, which is a financial transaction moving real monetary value. It is irreversible once broadcast to the Solana network. The blast radius is critical because an AI agent could drain the entire SOL balance of a derived address with a single call.
From the tool's definition Send native SOL from a Chain-Signature-derived Solana address... Amount in lamports (1 SOL = 1,000,000,000 lamports)
Documented attack patterns abuse exactly the kind of access hydra_send_solana gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Near Hydra, and nothing reaches the server without passing your rules. This is the rule we recommend for hydra_send_solana:
{
"version": "1",
"default": "deny",
"tools": {
"hydra_send_solana": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
}Any call to hydra_send_solana is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Send native SOL from a Chain-Signature-derived Solana address. SAFE: dry=true returns the plan. Amount in lamports (1 SOL = 1,000,000,000 lamports). Requires the derived address to have SOL. It is categorised as a Financial tool in the Near Hydra MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Near Hydra MCP server in PolicyLayer and add a rule for hydra_send_solana: 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 Near Hydra. Nothing to install.
hydra_send_solana 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 hydra_send_solana 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 hydra_send_solana. 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.
hydra_send_solana is provided by the Near Hydra MCP server (nikshepsvn/near-hydra). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Near Hydra, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 Near Hydra tools catalogued and risk-classified — across an index of 43,000+ MCP servers.