Get the current VIX (CBOE Volatility Index) alongside the CNN Fear & Greed composite index, with historical context showing whether current fear levels are extreme (contrarian buy) or extreme greed (contrarian sell). Use this tool when: - A trading agent wants to assess market risk temperature be...
AI agents call get_fear_index 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 tool retrieves financial market data (VIX and Fear & Greed index) for analysis and decision-support. It has no side effects—it does not execute trades, move funds, or modify state. However, severity is elevated to 'medium' rather than 'low' because the tool is explicitly designed to inform trading decisions in a financial context.
From the tool's definition Tool name is 'get_fear_index' and description explicitly states 'Get the current VIX...with historical context'. The verb 'Get' and lack of any modification, deletion, or execution language indicate this is a retrieval operation.
Attacks that exploit this kind of access
Get the current VIX (CBOE Volatility Index) alongside the CNN Fear & Greed composite index, with historical context showing whether current fear levels are extreme (contrarian buy) or extreme greed (contrarian sell). Use this tool when: - A trading agent wants to assess market risk temperature before taking positions - You need a quick single-metric read on whether the market is fearful or complacent - A risk management agent is calibrating position sizes based on volatility regime - An agent wants to detect contrarian opportunities (extreme fear = buy the dip opportunities) Returns: VIX (current, 30d_avg, 52w_high), fear_greed_index (0-100), fear_greed_label (EXTREME_FEAR/FEAR/NEUTRAL/GREED/EXTREME_GREED), historical_context, signal. Example: getFearIndex({ format:. 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_fear_index: 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_fear_index 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_fear_index 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_fear_index. 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_fear_index 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 →