Execute a token swap using Jupiter
AI agents invoke executeSwap to trigger actions in AMOCA Solana MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes irreversible blockchain transactions that move assets between token types. Although it is not strictly Financial (it doesn't directly move fiat money or create subscriptions), it is Execute because it triggers external operations whose effects are determined by supplied arguments.
From the tool's definition executeSwap performs a token swap using Jupiter, which triggers an external DeFi operation that commits blockchain transactions.
Attacks that exploit this kind of access
Execute a token swap using Jupiter. It is categorised as a Execute tool in the AMOCA Solana MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AMOCA Solana MCP Server MCP server in PolicyLayer and add a rule for executeSwap: 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 AMOCA Solana MCP Server. Nothing to install.
executeSwap is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the executeSwap 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 executeSwap. 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.
executeSwap is provided by the AMOCA Solana MCP Server MCP server (manolaz/amoca-solana-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 →