Generate a BUY, SELL, or HOLD signal for a trading instrument with full technical analysis: entry price, stop loss, take profit, risk-reward ratio, RSI, EMA stack, ATR, and confidence score. Use this tool when: - A trading agent needs a concrete entry/exit recommendation before placing a trade - ...
AI agents call get_trading_signal 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.
The tool retrieves and computes trading signals and technical analysis data — it does not itself execute trades or move money. However, it is explicitly designed as a precursor to trade execution ('before placing a trade', 'systematic trading strategy'), meaning misuse or blind trust in its output could lead to significant financial loss.
From the tool's definition Generate a BUY, SELL, or HOLD signal... entry price, stop loss, take profit, risk-reward ratio, RSI, EMA stack, ATR, and confidence score
Attacks that exploit this kind of access
Generate a BUY, SELL, or HOLD signal for a trading instrument with full technical analysis: entry price, stop loss, take profit, risk-reward ratio, RSI, EMA stack, ATR, and confidence score. Use this tool when: - A trading agent needs a concrete entry/exit recommendation before placing a trade - You want to validate a trading idea with technical indicators - An agent is running a systematic trading strategy and needs fresh signals - You need to know the current momentum, trend direction, and volatility for a symbol Supported symbols: XAUUSD (Gold), BTCUSD, ETHUSD, EURUSD, GBPUSD, USDJPY, NVDA, SPY, QQQ, and most major FX/crypto pairs. Supported timeframes: 1m, 5m, 15m, 30m, 1h, 4h, 1d, 1w. Returns: signal (BUY/SELL/HOLD), entry_price, stop_loss, take_profit, risk_reward_ratio, confidence (0-100), RSI, EMA_20, EMA_50, ATR, trend_direction, key_levels. Example: getTradingSignal({ 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_trading_signal: 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_trading_signal 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_trading_signal 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_trading_signal. 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_trading_signal 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 →