Use this when you need to retrieve funding payment history for a Hyperliquid perpetuals account. Returns all funding rate payments received or paid, useful for calculating funding income/expense and evaluating carry trade profitability. Returns: 1. coin: the perpetual market (BTC, ETH, SOL, etc.)...
Part of the HL Portfolio API server.
Free to start. No card required.
AI agents call hyperliquid_get_user_funding 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_user_funding 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.
{
"version": "1",
"default": "deny",
"tools": {
"hyperliquid_get_user_funding": {}
}
}See the full HL Portfolio API policy for all 4 tools.
These attack patterns abuse exactly the kind of access hyperliquid_get_user_funding gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Use this when you need to retrieve funding payment history for a Hyperliquid perpetuals account. Returns all funding rate payments received or paid, useful for calculating funding income/expense and evaluating carry trade profitability. Returns: 1. coin: the perpetual market (BTC, ETH, SOL, etc.) 2. fundingRate: the funding rate applied (positive = longs pay shorts) 3. payment: USD amount received (positive) or paid (negative) 4. timestamp: when the funding payment occurred 5. positionSize: the position size at time of funding Example output: { funding: [{ coin: "BTC", fundingRate: "0.0001", payment: "-1.35", timestamp: 1712000000000, positionSize: "1.5" }], totalReceived: "45.20", totalPaid: "-12.30", netFunding: "32.90" } Use this to evaluate funding income for carry/basis trades, calculate total cost of holding positions, or analyze the profitability of a delta-neutral funding strategy on Hyperliquid. Do NOT use for current positions -- use hyperliquid_get_account_state instead. Do NOT use for market-wide funding rates -- use hyperliquid_get_funding_rates instead. Do NOT use for funding arbitrage opportunities -- use funding_arb_find_opportunities instead. Do NOT use for trade execution history -- use hyperliquid_get_trade_fills instead.. It is categorised as a Read tool in the HL Portfolio API MCP Server, which means it retrieves data without modifying state.
Register the HL Portfolio API MCP server in PolicyLayer and add a rule for hyperliquid_get_user_funding: 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.
hyperliquid_get_user_funding 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 hyperliquid_get_user_funding 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 hyperliquid_get_user_funding. 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.
hyperliquid_get_user_funding 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.
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.