getFundingRateHistory
Query historical funding rate records for perpetual contracts.\nEach symbol has a different funding settlement interval (typically every 4 or 8 hours).\n\nUse this endpoint when you need to:\n- Analyze historical funding rate trends for a specific perpetual contract\n- Calculate total funding cos...
This record as markdown: /tools/bybit-exchange-trading-mcp/getfundingratehistory.md
What getFundingRateHistory does on Bybit MCP Server
AI agents call getFundingRateHistory to retrieve information from Bybit MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why getFundingRateHistory is rated Low
This tool retrieves historical data from the Bybit exchange without creating, modifying, deleting, or executing any operations. It has no blast radius if misused by an AI agent — worst case, it returns data about funding rates. No financial transactions, state changes, or external operations are triggered.
From the tool's definition Tool name 'getFundingRateHistory' and description explicitly states 'Query historical funding rate records' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs getFundingRateHistory safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Bybit MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getFundingRateHistory, this is the rule to start with:
getFundingRateHistory 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 Bybit MCP Server, apply this rule, and every getFundingRateHistory call is checked against it from then on.
Questions about getFundingRateHistory
Query historical funding rate records for perpetual contracts.\nEach symbol has a different funding settlement interval (typically every 4 or 8 hours).\n\nUse this endpoint when you need to:\n- Analyze historical funding rate trends for a specific perpetual contract\n- Calculate total funding cost or income for a position over a time period\n- Compare funding rates across different symbols or time periods\n\nSupported Products: USDT contract, Inverse contract\n\nRecords are sorted in reverse chronological order. Use. It is categorised as a Read tool in the Bybit MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bybit MCP Server MCP server in PolicyLayer and add a rule for getFundingRateHistory: 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 Bybit MCP Server. Nothing to install.
getFundingRateHistory 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 getFundingRateHistory 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 getFundingRateHistory. 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.
getFundingRateHistory is provided by the Bybit MCP Server MCP server (bybit-exchange/trading-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Bybit MCP Server, and thousands of servers like it.
This server
Across the catalogue