Execute 4-hop token swap via swap-helper-c (X->Y->Z->W->V)
AI agents use alex_execute_swap_4hop to commit financial operations through Stacks AI MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool executes a multi-hop token swap on a DeFi protocol, directly moving financial assets across four intermediate trading pairs. This constitutes a financial transaction with real monetary value at risk. Misuse could result in significant financial loss through slippage, incorrect routing, or malicious token substitution across four hops, giving it a critical blast radius.
From the tool's definition Execute 4-hop token swap via swap-helper-c (X->Y->Z->W->V)
Attacks that exploit this kind of access
Execute 4-hop token swap via swap-helper-c (X->Y->Z->W->V). It is categorised as a Financial tool in the Stacks AI MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Stacks AI MCP Server MCP server in PolicyLayer and add a rule for alex_execute_swap_4hop: 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_4hop 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 alex_execute_swap_4hop 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_4hop. 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_4hop 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.
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 →