get_funding_rate_history
AI agents call get_funding_rate_history to retrieve information from Aster Info without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Funding rate history is market data that can be queried but not modified. The tool retrieves information about past funding rates on a DEX, analogous to getting historical price data or order book snapshots. This has no side effects, cannot modify state, and only returns informational data. The broader server is a read-only market data provider.
From the tool's definition Tool name 'get_funding_rate_history' and server context indicates data retrieval. The server description explicitly states it provides 'structured access to Aster DEX market data' covering 'funding rates' and similar tools (get_kline, get_order_book,…
Attacks that exploit this kind of access
get_funding_rate_history. It is categorised as a Read tool in the Aster Info MCP Server, which means it retrieves data without modifying state.
Register the Aster Info 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 Aster Info. 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 Aster Info MCP server (kukapay/aster-info-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 →