get_funding_rate_history
A read tool on the Binance MCP server.
This record as markdown: /tools/mixuechu-binance-mcp/get-funding-rate-history.md
What get_funding_rate_history does on Binance MCP Server
AI agents call get_funding_rate_history to retrieve information from Binance 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 get_funding_rate_history is rated Low
This tool retrieves historical funding rate data from Binance, which is a read-only operation with no side effects. While it exists in a financial trading context (Binance cryptocurrency exchange), the tool itself merely fetches and returns data without moving money, executing trades, or modifying account state.
From the tool's definition Tool name 'get_funding_rate_history' and description 'Get funding rate history' indicate a retrieval operation that queries historical funding rate data without modifying state or executing trades.
Attacks that exploit this kind of access
The rule that runs get_funding_rate_history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Binance MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_funding_rate_history, this is the rule to start with:
get_funding_rate_history 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 Binance MCP Server, apply this rule, and every get_funding_rate_history call is checked against it from then on.
Questions about get_funding_rate_history
get_funding_rate_history is a read tool on the Binance MCP Server MCP server. It is categorised as a Read tool in the Binance MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Binance MCP Server 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 Binance MCP Server. 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 Binance MCP Server MCP server (mixuechu/binance-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Binance MCP Server, and thousands of servers like it.
This server
Across the catalogue