alex_execute_swap_3hop
Execute 3-hop token swap via swap-helper-b (X->Y->Z->W)
This record as markdown: /tools/stack-ai-mcp-stacks-mcp-server/alex-execute-swap-3hop.md
What alex_execute_swap_3hop does on Stacks AI MCP Server
AI agents invoke alex_execute_swap_3hop to trigger actions in Stacks AI 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.
Why alex_execute_swap_3hop is rated High
This tool executes a complex blockchain transaction (a 3-hop swap) that triggers external operations on the Stacks DeFi ecosystem. While it is not strictly destructive (the user retains the output tokens), it is Execute-category because: (1) it runs an external operation whose effects depend on provided arguments (token pairs, amounts); (2) it commits financial assets to a transaction path; (3) misuse could result…
From the tool's definition Execute 3-hop token swap via swap-helper-b (X->Y->Z->W) - the tool executes a multi-step swap transaction that irreversibly moves tokens across three trading pairs, with outcomes dependent on market conditions and arguments provided.
Attacks that exploit this kind of access
The rule that runs alex_execute_swap_3hop safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stacks AI MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For alex_execute_swap_3hop, this is the rule to start with:
alex_execute_swap_3hop stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Stacks AI MCP Server, apply this rule, and every alex_execute_swap_3hop call is checked against it from then on.
Questions about alex_execute_swap_3hop
Execute 3-hop token swap via swap-helper-b (X->Y->Z->W). It is categorised as a Execute tool in the Stacks AI MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Stacks AI MCP Server MCP server in PolicyLayer and add a rule for alex_execute_swap_3hop: 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 Stacks AI MCP Server. Nothing to install.
alex_execute_swap_3hop 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 alex_execute_swap_3hop 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 alex_execute_swap_3hop. 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.
alex_execute_swap_3hop is provided by the Stacks AI MCP Server MCP server (stack-ai-mcp/stacks-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stacks AI MCP Server, and thousands of servers like it.
Across the catalogue