Detect unusual options activity — large block trades, sweeps, and dark pool prints that may signal institutional positioning. Identifies volume/open-interest spikes and classifies them as bullish or bearish. Use this tool when: - A trading agent wants to follow institutional options flow as a lea...
AI agents call get_options_flow 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 performs data retrieval and analysis of public/semi-public options market information. While the underlying data concerns financial markets and could inform trading decisions, the tool itself does not execute trades, move funds, or commit financial obligations—it only reads and interprets market data. The 'Read' category applies because the core function is detection and analysis without side effects.
From the tool's definition Tool retrieves and analyzes options market data: 'Detect unusual options activity', 'Identifies volume/open-interest spikes', 'Returns per flow: ticker, expiry, strike, type'.
Attacks that exploit this kind of access
Detect unusual options activity — large block trades, sweeps, and dark pool prints that may signal institutional positioning. Identifies volume/open-interest spikes and classifies them as bullish or bearish. Use this tool when: - A trading agent wants to follow institutional options flow as a leading signal - You need to detect if smart money is buying calls (bullish) or puts (bearish) at scale - An agent is scanning for unusual activity before earnings or major events - You want to identify dark pool sweeps that suggest directional bets Returns per flow: ticker, expiry, strike, type (CALL/PUT), premium_usd, volume, open_interest, vol_oi_ratio, trade_type (SWEEP/BLOCK), sentiment (BULLISH/BEARISH), time. Example: getOptionsFlow({ 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_options_flow: 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_options_flow 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_options_flow 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_options_flow. 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_options_flow 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 →