AI agents call get_funding_rate_history to retrieve information from Bybit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical funding rate information from the Bybit exchange, which is a standard market data query operation. It has no side effects—it does not execute trades, move funds, create orders, or modify account state. While it operates in a financial domain, it is purely informational retrieval, not a financial action like a trade or transfer.
From the tool's definition Tool name 'get_funding_rate_history' indicates retrieval of historical funding rate data with no parameters that modify state. The 'get' verb and 'history' suffix are strongly characteristic of read-only query operations on a financial exchange.
Attacks that exploit this kind of access
get_funding_rate_history. It is categorised as a Read tool in the Bybit MCP Server, which means it retrieves data without modifying state.
Register the Bybit MCP server in PolicyLayer and add a rule for get_funding_rate_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 Bybit. Nothing to install.
get_funding_rate_history 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_funding_rate_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.
Set action: deny in the PolicyLayer policy for get_funding_rate_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.
get_funding_rate_history is provided by the Bybit MCP server (johnnywic/bybit-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 →