Fetch crypto futures and options market data: funding rates (positive = longs paying shorts), open interest trends, recent liquidations, and basis (spot vs futures premium/discount). Use this tool when: - A crypto trading agent needs to assess sentiment via funding rates (high positive = overleve...
AI agents call get_crypto_derivatives to retrieve information from Omni Service Node without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a Read operation: it queries external market data and returns analytics (funding rates, open interest, liquidations, basis spreads) without modifying any state. However, severity is elevated to 'medium' rather than 'low' because the tool provides real-time market intelligence that directly informs financial trading decisions.
From the tool's definition Tool fetches and retrieves crypto derivatives market data: 'Fetch crypto futures and options market data', 'funding rates', 'open interest trends', 'recent liquidations', 'basis'. All operations are queries with no side effects—data retrieval only.
Attacks that exploit this kind of access
Fetch crypto futures and options market data: funding rates (positive = longs paying shorts), open interest trends, recent liquidations, and basis (spot vs futures premium/discount). Use this tool when: - A crypto trading agent needs to assess sentiment via funding rates (high positive = overleveraged longs = bearish contrarian) - You want to detect potential short/long squeezes via open interest changes - An agent is managing a delta-neutral position and needs accurate funding cost - You need to know which exchanges have the most derivatives activity and liquidity Returns: funding_rate (8h), annualised_funding_pct, open_interest_usd, oi_change_24h_pct, liquidations_24h_usd (longs/shorts), basis_pct, perpetual_vs_quarterly_premium, dominant_exchange. Example: getCryptoDerivatives({ symbol:. It is categorised as a Read tool in the Omni Service Node MCP Server, which means it retrieves data without modifying state.
Register the Omni Service Node MCP server in PolicyLayer and add a rule for get_crypto_derivatives: 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 Omni Service Node. Nothing to install.
get_crypto_derivatives 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_crypto_derivatives 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_crypto_derivatives. 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_crypto_derivatives is provided by the Omni Service Node MCP server (luckkyyy23/omni-service-node). 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 →