jupiter_swap
Execute a token swap via Jupiter v6 aggregator. Best-route swap across all Solana DEXes. Requires AGENTI_SOLANA_PRIVATE_KEY.
This record as markdown: /tools/nirholas-agenti/jupiter-swap.md
What jupiter_swap does on Agenti
AI agents use jupiter_swap to commit financial operations through Agenti, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why jupiter_swap is rated Critical
This tool performs an on-chain cryptocurrency token swap using a private key, which directly moves financial assets. It falls squarely in the Financial category (trading/swapping tokens). The blast radius is critical because it can irreversibly exchange potentially large amounts of cryptocurrency with no undo mechanism, using the user's private key to sign and broadcast transactions to the Solana blockchain.
From the tool's definition Execute a token swap via Jupiter v6 aggregator. Best-route swap across all Solana DEXes. Requires AGENTI_SOLANA_PRIVATE_KEY.
Attacks that exploit this kind of access
The rule that runs jupiter_swap safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Agenti, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For jupiter_swap, this is the rule to start with:
Any call to jupiter_swap is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Agenti, apply this rule, and every jupiter_swap call is checked against it from then on.
Questions about jupiter_swap
Execute a token swap via Jupiter v6 aggregator. Best-route swap across all Solana DEXes. Requires AGENTI_SOLANA_PRIVATE_KEY. It is categorised as a Financial tool in the Agenti MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Agenti MCP server in PolicyLayer and add a rule for jupiter_swap: 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 Agenti. Nothing to install.
jupiter_swap 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 jupiter_swap 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 jupiter_swap. 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.
jupiter_swap is provided by the Agenti MCP server (nirholas/agenti). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Agenti, and thousands of servers like it.
Across the catalogue