Execute multihop swap via Blaze routing
AI agents use charisma_execute_multihop_swap 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 token swaps on a DeFi protocol, which involves moving financial assets (tokens) across multiple hops. Swaps are financial transactions that commit real value on-chain and are irreversible once broadcast to the blockchain. The server context confirms this operates on a live DeFi ecosystem on Stacks Bitcoin Layer 2, making misuse potentially catastrophic for user funds.
From the tool's definition Execute multihop swap via Blaze routing
Attacks that exploit this kind of access
Execute multihop swap via Blaze routing. 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 charisma_execute_multihop_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 Stacks AI MCP Server. Nothing to install.
charisma_execute_multihop_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 charisma_execute_multihop_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 charisma_execute_multihop_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.
charisma_execute_multihop_swap 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 →