Get the current market risk appetite: Fear & Greed index, global crypto market data, live asset prices, trending tokens, and a RISK_ON/RISK_OFF signal. Use this tool when: - An agent needs to determine whether market conditions favour risk-on (buy) or risk-off (sell/hedge) positioning - A trading...
AI agents call get_market_sentiment 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-only data retrieval tool. It provides market sentiment indicators and pricing information without executing trades, modifying data, or committing financial obligations. While the use case describes agents making trading decisions, the tool itself only supplies information.
From the tool's definition Tool retrieves current market data: 'Fear & Greed index, global crypto market data, live asset prices, trending tokens, and a RISK_ON/RISK_OFF signal' and 'Returns: fear_greed_index, global_market_cap, BTC_dominance, asset_prices, 24h_change'.
Attacks that exploit this kind of access
Get the current market risk appetite: Fear & Greed index, global crypto market data, live asset prices, trending tokens, and a RISK_ON/RISK_OFF signal. Use this tool when: - An agent needs to determine whether market conditions favour risk-on (buy) or risk-off (sell/hedge) positioning - A trading agent wants a high-level market pulse before executing orders - A portfolio agent is deciding whether to increase or reduce exposure - You need to know what tokens/assets are trending and why Returns: fear_greed_index (0-100, 0=extreme fear), global_market_cap, BTC_dominance, asset_prices, 24h_changes, trending_tokens, overall_signal (RISK_ON/RISK_OFF/NEUTRAL). Example: getMarketSentiment({ assets:. 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_market_sentiment: 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_market_sentiment 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_market_sentiment 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_market_sentiment. 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_market_sentiment 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 →