Get user's fee information from Hyperliquid exchange.
AI agents call get_user_fees 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 fee information associated with a user account. Retrieving account metadata and fee tiers is a read-only operation with no side effects—it does not create, modify, delete, or execute any orders or financial transactions. Even in the context of a trading platform, querying fee information poses minimal risk compared to tools that execute trades, cancel orders, or move funds.
From the tool's definition Tool name 'get_user_fees' and description 'Get user's fee information from Hyperliquid exchange' indicate retrieval of existing data with no modification, creation, deletion, or execution of trades.
Attacks that exploit this kind of access
Get user's fee information 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_fees: 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_fees 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_fees 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_fees. 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_fees 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 →