market_bars
Historical OHLCV bars. Free via public data (best-effort); BYOK Alpaca for reliable IEX bars. Returns {ok, symbol, source, count, bars:[{t,o,h,l,c,v}]}.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/market-bars.md
What market_bars does on Gateway
AI agents call market_bars to retrieve information from Gateway 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 |
|---|---|---|---|
limit | integer | — | BYOK Alpaca: max bars (default 200) |
range | string | — | free-tier window: 1d/5d/1mo/3mo/6mo/1y/… (default 1mo) |
handle | string | — | |
secret | string | — | |
symbol | string | Yes | ticker |
key_ref | string | — | |
interval | string | — | free-tier bar size: 1m/5m/1h/1d/1wk/… (default 1d) |
timeframe | string | — | BYOK Alpaca bar size: 1Min/1Hour/1Day/… (default 1Day) |
alpaca_key_id | string | — | |
alpaca_secret | string | — |
Parameters from the server's own tool schema.
Why market_bars is rated Low
This is a data query tool that retrieves market price history. It has no side effects, does not execute trades, does not modify data, and does not commit financial obligations. The 'BYOK Alpaca' integration is a configuration option for data source reliability, not a financial action.
From the tool's definition Tool returns historical OHLCV bars with no modification capability—'Returns {ok, symbol, source, count, bars:[{t,o,h,l,c,v}]}'. Data retrieval only, explicitly fetches 'Historical OHLCV bars'.
Risk signalsHandles credentials or secrets (secret) · High parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs market_bars safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For market_bars, this is the rule to start with:
market_bars 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 Gateway, apply this rule, and every market_bars call is checked against it from then on.
Questions about market_bars
Historical OHLCV bars. Free via public data (best-effort); BYOK Alpaca for reliable IEX bars. Returns {ok, symbol, source, count, bars:[{t,o,h,l,c,v}]}. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
market_bars accepts 10 parameters: limit, range, handle, secret, symbol, key_ref, interval, timeframe, alpaca_key_id, alpaca_secret. Required: symbol. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for market_bars: 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 Gateway. Nothing to install.
market_bars 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 market_bars 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 market_bars. 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.
market_bars is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue