AI agents invoke dex_build_swap to trigger actions in Logiqical. 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 constructs unsigned swap transactions on a blockchain, which is an Execute action—it prepares code/operations whose effects (token swaps) depend on arguments and subsequent signing/broadcast. While financially consequential, the tool itself does not move funds; it builds the transaction structure.
From the tool's definition Tool name 'dex_build_swap' and description 'Build unsigned swap transactions' indicate constructing and preparing blockchain transactions for execution.
Attacks that exploit this kind of access
Build unsigned swap transactions (1 tx for AVAX→token, 2 txs otherwise). It is categorised as a Execute tool in the Logiqical MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Logiqical MCP server in PolicyLayer and add a rule for dex_build_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 Logiqical. Nothing to install.
dex_build_swap 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 dex_build_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 dex_build_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.
dex_build_swap is provided by the Logiqical MCP server (logiqical-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
dex_build_swap is one line of Logiqical's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →