Get funding rate history for a COIN-M Futures perpetual contract.
AI agents call BinanceDeliveryFundingRate to retrieve information from BNB Chain MCP 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 data for futures perpetual contracts. It performs a query operation with no capability to modify, execute, delete, or transfer assets. The action is purely informational—fetching historical metrics about financial instruments rather than executing trades or moving funds. This is a low-severity Read operation appropriate for market data analysis.
From the tool's definition Tool name 'BinanceDeliveryFundingRate' and description 'Get funding rate history' indicate data retrieval with no side effects. The verb 'Get' and 'history' are characteristic of Read operations that query existing data without modification.
Documented attack patterns abuse exactly the kind of access BinanceDeliveryFundingRate gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and BNB Chain MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for BinanceDeliveryFundingRate:
{
"version": "1",
"default": "deny",
"tools": {
"BinanceDeliveryFundingRate": {}
}
}BinanceDeliveryFundingRate is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get funding rate history for a COIN-M Futures perpetual contract. It is categorised as a Read tool in the BNB Chain MCP MCP Server, which means it retrieves data without modifying state.
Register the BNB Chain MCP server in PolicyLayer and add a rule for BinanceDeliveryFundingRate: 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 BNB Chain MCP. Nothing to install.
BinanceDeliveryFundingRate 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 BinanceDeliveryFundingRate 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 BinanceDeliveryFundingRate. 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.
BinanceDeliveryFundingRate is provided by the BNB Chain MCP server (nirholas/bnbchain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 1240 BNB Chain MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
1240 BNB Chain MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.