compare_funding_rates
chainpeek: Compare perpetual funding rates between Hyperliquid and dYdX. For five venues net of fees use rank_funding_carry. Returns each venue's hourly and annualised funding and the spread (Hyperliquid minus dYdX v4), ranked by absolute spread. Only assets on both venues are compared; the other...
This record as markdown: /tools/dev-tanod-tanod/compare-funding-rates.md
What compare_funding_rates does on Tanod
AI agents call compare_funding_rates to retrieve information from Tanod without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Rows returned, 1-50 (default 10). |
symbols | object | — | Optional: only these base assets (case-insensitive, at most 50), such as BTC. Names not listed on both venues are returned in symbols_not_found. |
min_volume_usd | number | — | Skip markets whose 24 h volume on either venue is below this (USD). Default 0. |
Parameters from the server's own tool schema.
Why compare_funding_rates is rated Low
Even though compare_funding_rates only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs compare_funding_rates safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tanod, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For compare_funding_rates, this is the rule to start with:
compare_funding_rates is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tanod, apply this rule, and every compare_funding_rates call is checked against it from then on.
Questions about compare_funding_rates
chainpeek: Compare perpetual funding rates between Hyperliquid and dYdX. For five venues net of fees use rank_funding_carry. Returns each venue's hourly and annualised funding and the spread (Hyperliquid minus dYdX v4), ranked by absolute spread. Only assets on both venues are compared; the others come back in symbols_not_found, and min_volume_usd must be met on both. Cached up to 60 s. Data only, not trading advice. Bad input is a 422 (not charged). Typically 0.3-2 s. Price: USD 0.003. Free: 10 chain reads per IP per UTC day. Docs: https://tanod.dev/learn/funding-rate-spread-api.html. It is categorised as a Read tool in the Tanod MCP Server, which means it retrieves data without modifying state.
compare_funding_rates accepts 3 parameters: limit, symbols, min_volume_usd. The full parameter table on this page comes from the server's own tool schema.
Register the Tanod MCP server in PolicyLayer and add a rule for compare_funding_rates: 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 Tanod. Nothing to install.
compare_funding_rates 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 compare_funding_rates 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 compare_funding_rates. 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.
compare_funding_rates is provided by the Tanod MCP server (https://tanod.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tanod, and thousands of servers like it.
This server
Across the catalogue