Execute an end-to-end cross-chain swap via NEAR Intents 1Click. Auto-routes the origin send by asset: NEAR-side FTs use ft_transfer; bridged EVM (ETH/ARB/BASE/POL/BSC/OP/AVAX/Aurora) routes through send_evm using a derived foreign-chain address; native BTC and SOL use their native sends; SPL toke...
AI agents use hydra_swap_execute 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 moves crypto assets across blockchains by executing swaps and sending tokens to deposit addresses. It directly commits financial transactions involving real assets (BTC, ETH, SOL, NEAR, and other tokens) across 10 blockchains. Misuse could result in irreversible loss of funds at critical scale.
From the tool's definition Execute an end-to-end cross-chain swap via NEAR Intents 1Click... send the origin asset to the depositAddress, and submit the deposit hash
Documented attack patterns abuse exactly the kind of access hydra_swap_execute 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_swap_execute:
{
"version": "1",
"default": "deny",
"tools": {
"hydra_swap_execute": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to hydra_swap_execute is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Execute an end-to-end cross-chain swap via NEAR Intents 1Click. Auto-routes the origin send by asset: NEAR-side FTs use ft_transfer; bridged EVM (ETH/ARB/BASE/POL/BSC/OP/AVAX/Aurora) routes through send_evm using a derived foreign-chain address; native BTC and SOL use their native sends; SPL tokens (nep141:sol-{mint}.omft.near) route through send_spl with auto-ATA creation. SAFE: dry=true returns the inferred route + previewed quote request. Set dry=false to fetch a non-dry quote, send the origin asset to the depositAddress, and submit the deposit hash. Pre-conditions: derived address must hold the origin asset + native gas on its chain; NEAR account pays for the MPC sign request. 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_swap_execute: 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_swap_execute 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_swap_execute 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_swap_execute. 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_swap_execute 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.