Low Risk

hyperliquid_get_funding_history

Use this when you need historical funding rate data for a specific Hyperliquid perpetual market. Returns timestamped funding rate entries over a configurable lookback window, plus summary statistics including average, min, max, and standard deviation. Data returned: 1. coin: the queried ticker sy...

Part of the Hyperliquid Funding Rates API server.

hyperliquid_get_funding_history 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 HYPERLIQUID FUNDING RATES API →

Free to start. No card required.

AI agents call hyperliquid_get_funding_history to retrieve information from Hyperliquid Funding Rates 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_funding_history 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_funding_history": {}
  }
}

See the full Hyperliquid Funding Rates API policy for all 3 tools.

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

ENFORCE ON MY HYPERLIQUID FUNDING RATES API →

These attack patterns abuse exactly the kind of access hyperliquid_get_funding_history 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_funding_history only ever does what you allow.

SECURE HYPERLIQUID FUNDING RATES 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_funding_history tool do? +

Use this when you need historical funding rate data for a specific Hyperliquid perpetual market. Returns timestamped funding rate entries over a configurable lookback window, plus summary statistics including average, min, max, and standard deviation. Data returned: 1. coin: the queried ticker symbol (e.g. BTC, ETH, SOL) 2. hours: lookback period requested (default 24) 3. entries: array of { time (ISO 8601), fundingRate (decimal), annualizedRate (%) } 4. summary.count: number of funding periods in the window 5. summary.avgRate: average funding rate over the period 6. summary.avgAnnualized: average annualized rate (%) 7. summary.minRate / maxRate: extremes observed in the window 8. summary.stdDev: standard deviation of rates (volatility of funding) Example output: { coin: "ETH", hours: 24, entries: [{ time: "2026-04-13T08:00:00Z", fundingRate: 0.0001, annualizedRate: 10.95 }, ...], summary: { count: 3, avgRate: 0.00012, avgAnnualized: 13.14, minRate: 0.00008, maxRate: 0.00015, stdDev: 0.000029 } } Use this to analyze funding trends before entering a carry trade or to backtest funding-based strategies over recent periods. Do NOT use for current rates across all markets -- use hyperliquid_get_funding_rates instead. Do NOT use for on-chain wallet analysis -- use wallet_get_portfolio instead. Do NOT use for CEX funding rates -- use funding_rates_get_current instead.. It is categorised as a Read tool in the Hyperliquid Funding Rates API MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on hyperliquid_get_funding_history? +

Register the Hyperliquid Funding Rates API MCP server in PolicyLayer and add a rule for hyperliquid_get_funding_history: 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 Funding Rates API. Nothing to install.

What risk level is hyperliquid_get_funding_history? +

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

Can I rate-limit hyperliquid_get_funding_history? +

Yes. Add a rate_limit block to the hyperliquid_get_funding_history 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_funding_history completely? +

Set action: deny in the PolicyLayer policy for hyperliquid_get_funding_history. 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_funding_history? +

hyperliquid_get_funding_history is provided by the Hyperliquid Funding Rates API MCP server (https://hl-funding.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 Hyperliquid Funding Rates API tool call.

Deterministic rules across all 3 Hyperliquid Funding Rates 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.