realtime_data_streams
High-frequency real-time market data for trading agents, market-making bots and fintech analysts. Returns FX ticks (bid/ask/spread), intraday OHLCV candles, crypto orderbook snapshots (depth 5-50), recent trades with VWAP, and sovereign bond yields. All sources are keyless public REST APIs (Binan...
This record as markdown: /tools/io-github-getgapup-mcp-knowledge/realtime-data-streams.md
What realtime_data_streams does on Mcp Knowledge
AI agents call realtime_data_streams to retrieve information from Mcp Knowledge without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
mode | string | Yes | Data stream type: fx_tick (latest FX bid/ask/mid/spread), fx_history_intraday (OHLCV candles), crypto_orderbook (order book snapshot), crypto_trades_recent (las |
async | boolean | — | If true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client ti |
depth | number | — | Orderbook depth (levels each side) for crypto_orderbook mode (default: 20) |
period | string | — | Candle period for fx_history_intraday mode (default: 5m) |
symbol | string | Yes | Market symbol. FX: EURUSD, GBPUSD, USDJPY. Crypto: BTCUSDT, ETHUSDT, BTC-USD. Bonds: US10Y, US2Y, DE10Y, FR10Y, UK10Y, JP10Y, IT10Y |
Parameters from the server's own tool schema.
Why realtime_data_streams is rated Low
This tool retrieves real-time market data without modifying any state or executing financial transactions. While the data fuels trading decisions and the tool is deployed in fintech contexts (raising severity above 'low' due to potential for misuse in high-frequency trading or market manipulation if an agent uses stale/incorrect data), the tool itself only performs read operations.
From the tool's definition Tool returns 'FX ticks (bid/ask/spread), intraday OHLCV candles, crypto orderbook snapshots, recent trades with VWAP, and sovereign bond yields' from 'keyless public REST APIs' with no mention of order placement, execution, settlement, or any state-changing…
Attacks that exploit this kind of access
The rule that runs realtime_data_streams safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Knowledge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For realtime_data_streams, this is the rule to start with:
realtime_data_streams is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Knowledge, apply this rule, and every realtime_data_streams call is checked against it from then on.
Questions about realtime_data_streams
High-frequency real-time market data for trading agents, market-making bots and fintech analysts. Returns FX ticks (bid/ask/spread), intraday OHLCV candles, crypto orderbook snapshots (depth 5-50), recent trades with VWAP, and sovereign bond yields. All sources are keyless public REST APIs (Binance, Coinbase, Kraken, OKX, open FX feeds, worldgovernmentbonds.com). Ultra-short cache: 10s for ticks/trades, 60s for orderbook. Use when an agent needs live market data as precise numeric inputs for trading logic, arbitrage detection, or portfolio valuation. It is categorised as a Read tool in the Mcp Knowledge MCP Server, which means it retrieves data without modifying state.
realtime_data_streams accepts 5 parameters: mode, async, depth, period, symbol. Required: mode, symbol. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Knowledge MCP server in PolicyLayer and add a rule for realtime_data_streams: 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 Mcp Knowledge. Nothing to install.
realtime_data_streams 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 realtime_data_streams 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 realtime_data_streams. 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.
realtime_data_streams is provided by the Mcp Knowledge MCP server (https://mcp.gapup.io). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Knowledge, and thousands of servers like it.
This server
Across the catalogue