Low Risk

hyperliquid_get_open_orders

Use this when you need to see all pending/open orders for a Hyperliquid perpetuals account. Returns every resting order on the book with full order parameters. Returns: 1. coin: the perpetual market (BTC, ETH, SOL, etc.) 2. side: buy (bid) or sell (ask) 3. limitPx: limit price of the order 4. sz:...

Risk signalsBulk/mass operation — affects multiple targets

Part of the HL Portfolio API server.

hyperliquid_get_open_orders is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE HL PORTFOLIO API →

Free to start. No card required.

AI agents call hyperliquid_get_open_orders to retrieve information from HL Portfolio API without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though hyperliquid_get_open_orders only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "hyperliquid_get_open_orders": {}
  }
}

See the full HL Portfolio API policy for all 4 tools.

Get this rule live on your own HL Portfolio API server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY HL PORTFOLIO API →

These attack patterns abuse exactly the kind of access hyperliquid_get_open_orders gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so hyperliquid_get_open_orders only ever does what you allow.

SECURE HL PORTFOLIO API →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the hyperliquid_get_open_orders tool do? +

Use this when you need to see all pending/open orders for a Hyperliquid perpetuals account. Returns every resting order on the book with full order parameters. Returns: 1. coin: the perpetual market (BTC, ETH, SOL, etc.) 2. side: buy (bid) or sell (ask) 3. limitPx: limit price of the order 4. sz: order size 5. orderType: limit, stop-market, stop-limit, take-profit, etc. 6. reduceOnly: whether the order can only reduce an existing position 7. timestamp: when the order was placed 8. oid: unique order ID Example output: { orders: [{ coin: "BTC", side: "buy", limitPx: "65000.00", sz: "0.5", orderType: "limit", reduceOnly: false, oid: 123456 }], count: 3 } Use this to understand a trader's pending strategy, detect limit orders near current price, evaluate order-to-position ratio, or monitor stop-loss placement on Hyperliquid. Do NOT use for executed trades -- use hyperliquid_get_trade_fills instead. Do NOT use for current positions -- use hyperliquid_get_account_state instead. Do NOT use for market-level orderbook -- use hyperliquid_get_market_data instead.. It is categorised as a Read tool in the HL Portfolio API MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on hyperliquid_get_open_orders? +

Register the HL Portfolio API MCP server in PolicyLayer and add a rule for hyperliquid_get_open_orders: 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 HL Portfolio API. Nothing to install.

What risk level is hyperliquid_get_open_orders? +

hyperliquid_get_open_orders is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit hyperliquid_get_open_orders? +

Yes. Add a rate_limit block to the hyperliquid_get_open_orders 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.

How do I block hyperliquid_get_open_orders completely? +

Set action: deny in the PolicyLayer policy for hyperliquid_get_open_orders. 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.

What MCP server provides hyperliquid_get_open_orders? +

hyperliquid_get_open_orders is provided by the HL Portfolio API MCP server (https://hl-portfolio.api.klymax402.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every HL Portfolio API tool call.

Deterministic rules across all 4 HL Portfolio API tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.