List all open positions with unrealized PnL, leverage, and liquidation price
AI agents call get_positions to retrieve information from Hyperliquid MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about existing positions (unrealized PnL, leverage, liquidation price) without modifying state. It is purely informational, making it a Read category tool with low severity since an agent misusing it cannot cause financial harm or unintended transactions.
From the tool's definition Tool description states "List all open positions" which is a retrieval operation with no side effects. No data modification, deletion, or execution of orders occurs.
Attacks that exploit this kind of access
List all open positions with unrealized PnL, leverage, and liquidation price. It is categorised as a Read tool in the Hyperliquid MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Hyperliquid MCP Server MCP server in PolicyLayer and add a rule for get_positions: 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 Hyperliquid MCP Server. Nothing to install.
get_positions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_positions 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 get_positions. 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.
get_positions is provided by the Hyperliquid MCP Server MCP server (samklein952-hub/hyperliquid-mcp). 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 →