Market Intelligence Pack — combines trading signals + on-chain data + macro + options flow + insider trades + earnings into a comprehensive market intelligence report. Best value for active trading agents. Use this tool when: - A trading agent wants a full-spectrum market view before sizing into ...
AI agents invoke run_bundle_market_intel to trigger actions in Omni Service Node. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool retrieves and aggregates market data (read-like operations) but is classified as Execute because: (1) it is explicitly designed to inform and trigger trading agent position-sizing decisions ('sizing into positions'), (2) the aggregated output directly drives financial transactions via downstream use by trading agents, and (3) market intelligence reports that combine options flow, insider trades, and…
From the tool's definition Combines trading signals + on-chain data + macro + options flow + insider trades + earnings into a comprehensive market intelligence report. Described as 'best value for active trading agents' sizing into positions.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Market Intelligence Pack — combines trading signals + on-chain data + macro + options flow + insider trades + earnings into a comprehensive market intelligence report. Best value for active trading agents. Use this tool when: - A trading agent wants a full-spectrum market view before sizing into positions - You need to cross-reference technical signals with institutional flow (options + insider) - An agent is doing pre-market prep and needs all data sources in one efficient call - A risk manager needs a complete market health assessment Returns: trading_signals (per symbol), onchain_metrics, macro_environment, unusual_options_flow, insider_buying_selling, upcoming_earnings_risks. Example: runBundleMarketIntel({ symbols: [. It is categorised as a Execute tool in the Omni Service Node MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Omni Service Node MCP server in PolicyLayer and add a rule for run_bundle_market_intel: 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.
run_bundle_market_intel is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_bundle_market_intel 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 run_bundle_market_intel. 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.
run_bundle_market_intel 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 →