AI agents call get_funding_rate_history to retrieve information from Coin without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves cryptocurrency funding rate history—market data without side effects. No modification, execution, deletion, or financial transactions occur. It is a straightforward data query fitting the 'Read' category. Confidence is slightly reduced due to the missing description, but the naming pattern and sibling tools strongly indicate read-only functionality.
From the tool's definition Tool name 'get_funding_rate_history' indicates retrieval of historical funding rate data. Sibling tools like 'compare_funding_rates', 'get_coin_tickers', 'get_coin_details', and 'get_aggregated_ohlc' are all data-retrieval operations consistent with a…
Attacks that exploit this kind of access
get_funding_rate_history. It is categorised as a Read tool in the Coin MCP Server, which means it retrieves data without modifying state.
Register the Coin 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 Coin. 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 Coin MCP server (sweetcornna/coin-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 →