Get recent user fills/trades from Hyperliquid exchange.
AI agents call get_user_fills to retrieve information from Hyperliquid without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical fill/trade data for the user. It queries past trading activity without creating, modifying, deleting, or executing any operations. While the Hyperliquid server enables trading operations, this particular tool is a data retrieval function that poses minimal risk if misused by an AI agent—it exposes account trading history but cannot execute trades, transfer funds, or modify data.
From the tool's definition Tool name is 'get_user_fills' and description states 'Get recent user fills/trades from Hyperliquid exchange.' The verb 'Get' and action of retrieving historical trade data indicates a read-only operation with no side effects.
Attacks that exploit this kind of access
Get recent user fills/trades from Hyperliquid exchange. It is categorised as a Read tool in the Hyperliquid MCP Server, which means it retrieves data without modifying state.
Register the Hyperliquid MCP server in PolicyLayer and add a rule for get_user_fills: 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. Nothing to install.
get_user_fills 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_user_fills 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_user_fills. 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_user_fills is provided by the Hyperliquid MCP server (midodimori/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 →