Uniswap Submit Limit Order
WarnAudited by ClawScan on May 10, 2026.
Overview
The skill matches its Uniswap trading purpose, but it can submit real financial orders without clearly requiring final user confirmation or bounding wallet, price, and spending safeguards.
Review carefully before installing or using. Only connect this skill to a wallet/MCP setup with limited permissions, require a visible final confirmation for every order, and verify the exact token pair, chain, amount, limit price, expiry, and spending limit before allowing submission.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
An agent could place an order at an unintended price or before the user reviews the final quote, potentially causing unwanted trades or financial loss.
For a real financial order, the workflow defaults the limit price instead of requiring it, does not list limitPrice or expiry in the submit call, and does not require a final user confirmation before submitting.
`limitPrice` | No | market price ... 3. **Submit order**: Call `submit_uniswapx_order` with: - tokenIn, tokenOut, amount, chain - orderType: "dutch"
Require explicit confirmation immediately before submission, show wallet, chain, token pair, amount, limit price, minimum output, expiry, fees/allowances, and include the validated limitPrice and expiry in the tool call.
If connected to a wallet or trading account with broad permissions, the agent may be able to create orders that spend user assets without clear containment.
The skill has delegated authority to submit wallet-affecting orders and references spending controls, but the artifacts do not define which wallet/account is used, what spending limits apply, or how approvals/cancellations are bounded.
allowed-tools: ... mcp__uniswap__submit_uniswapx_order ... 1. **Validate inputs**: Check token allowlist, spending limits, and UniswapX support on the target chain.
Document the wallet/account boundary, require user-selected accounts, enforce hard per-order and per-token spend limits, and explain allowance, signing, cancellation, and recovery behavior.
Trade details may be visible to or acted on by the configured MCP server or subagent.
The skill may route trade intent and order details through a Uniswap MCP integration and a trade-executor subagent. This is purpose-aligned, but the artifact does not identify the trust boundary or permissions for those integrations.
allowed-tools: ... Task(subagent_type:trade-executor), mcp__uniswap__get_quote, mcp__uniswap__submit_uniswapx_order ...
Use only trusted MCP servers/subagents, and document what data is sent and which component is authorized to sign or submit orders.
Installing from an unverified remote source could expose users to changed or different skill content outside the reviewed artifacts.
The reviewed artifact is instruction-only, but the README installation examples fetch remote content; users should verify the source because the registry metadata reports an unknown source and no homepage.
npx skills add https://github.com/wpank/Agentic-Uniswap/tree/main/.ai/skills/submit-limit-order ... npx clawhub@latest install submit-limit-order
Install from a trusted, pinned source or verify the repository and skill contents before installation.