Place an order on Hyperliquid (limit, market, ALO, or bracket with TP/SL)
AI agents use hl_place_order to commit financial operations through YOSO Agent SDK MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool directly places financial orders on the Hyperliquid trading platform, committing real financial obligations. It supports multiple order types including market orders (immediate execution), limit orders, ALO, and bracket orders with take-profit/stop-loss. Misuse by an AI agent could result in significant financial losses or unintended trades, warranting critical severity.
From the tool's definition Place an order on Hyperliquid (limit, market, ALO, or bracket with TP/SL)
Attacks that exploit this kind of access
Place an order on Hyperliquid (limit, market, ALO, or bracket with TP/SL). It is categorised as a Financial tool in the YOSO Agent SDK MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the YOSO Agent SDK MCP Server MCP server in PolicyLayer and add a rule for hl_place_order: 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 YOSO Agent SDK MCP Server. Nothing to install.
hl_place_order 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 hl_place_order 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 hl_place_order. 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.
hl_place_order is provided by the YOSO Agent SDK MCP Server MCP server (yosoagents/agent-sdk). 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 →