api_haystack_execute_swap
Execute an optimized token swap via Haystack Router — gets the best route across multiple DEXes (Tinyman V2, Pact, Folks) and LST protocols, then signs and submits the atomic transaction group using the active wallet account. This is an all-in-one tool: quote → sign → submit → confirm. All amount...
This record as markdown: /tools/goplausible-algorand-mcp/api-haystack-execute-swap.md
What api_haystack_execute_swap does on Algorand MCP
AI agents use api_haystack_execute_swap to commit financial operations through Algorand MCP, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why api_haystack_execute_swap is rated Critical
This tool executes a real token swap on-chain across DEXes, involving the signing and submission of financial transactions with the user's wallet. It moves crypto assets irreversibly, which qualifies as a Financial action. The all-in-one nature (no separate confirmation step) and use of the active wallet make misuse potentially critical in blast radius.
From the tool's definition Execute an optimized token swap...signs and submits the atomic transaction group using the active wallet account. This is an all-in-one tool: quote → sign → submit → confirm.
Attacks that exploit this kind of access
The rule that runs api_haystack_execute_swap safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Algorand MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For api_haystack_execute_swap, this is the rule to start with:
Any call to api_haystack_execute_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 Algorand MCP, apply this rule, and every api_haystack_execute_swap call is checked against it from then on.
Questions about api_haystack_execute_swap
Execute an optimized token swap via Haystack Router — gets the best route across multiple DEXes (Tinyman V2, Pact, Folks) and LST protocols, then signs and submits the atomic transaction group using the active wallet account. This is an all-in-one tool: quote → sign → submit → confirm. All amounts are in base units (e.g., 1000000 = 1 ALGO). It is categorised as a Financial tool in the Algorand MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Algorand MCP server in PolicyLayer and add a rule for api_haystack_execute_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 Algorand MCP. Nothing to install.
api_haystack_execute_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 api_haystack_execute_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 api_haystack_execute_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.
api_haystack_execute_swap is provided by the Algorand MCP server (goplausible/algorand-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Algorand, and thousands of servers like it.
Across the catalogue