Market-close a position on Hyperliquid
AI agents use hl_close_position 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.
Closing a market position on Hyperliquid is a financial trading action that executes a real trade to exit an open position, directly involving financial assets. This is irreversible once the market order is filled and has direct monetary consequences, making it a Financial category tool with critical severity.
From the tool's definition Market-close a position on Hyperliquid
Attacks that exploit this kind of access
Market-close a position on Hyperliquid. 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_close_position: 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_close_position 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_close_position 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_close_position. 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_close_position 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.
hl_close_position is one line of YOSO Agent SDK MCP Server'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 →