Get OHLCV candlestick data for a stock ticker — open, high, low, close, and volume. WHEN TO USE: For price chart analysis, pattern recognition, or feeding data into technical analysis. Use veroq_technicals for pre-computed indicators. RETURNS: Array of candles with date, open, high, low, close, v...
AI agents call veroq_candles to retrieve information from Veroq without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a data retrieval tool that queries and returns historical price information for technical analysis. It has no side effects, does not execute trades, does not modify data, and does not delete anything. The data returned is informational only.
From the tool's definition Tool retrieves historical OHLCV candlestick data (open, high, low, close, volume) for stock analysis. Description states 'Get...candlestick data' and 'RETURNS: Array of candles' with no mention of modifying, executing operations, deleting data, or financial…
Attacks that exploit this kind of access
Get OHLCV candlestick data for a stock ticker — open, high, low, close, and volume. WHEN TO USE: For price chart analysis, pattern recognition, or feeding data into technical analysis. Use veroq_technicals for pre-computed indicators. RETURNS: Array of candles with date, open, high, low, close, volume. Latest candle highlighted. COST: 2 credits. EXAMPLE: {. It is categorised as a Read tool in the Veroq MCP Server, which means it retrieves data without modifying state.
Register the Veroq MCP server in PolicyLayer and add a rule for veroq_candles: 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 Veroq. Nothing to install.
veroq_candles 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 veroq_candles 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 veroq_candles. 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.
veroq_candles is provided by the Veroq MCP server (veroq-ai/veroq-mcp). 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 →