Get all major technical indicators for a ticker: RSI, MACD, Bollinger Bands, moving averages, and overall signal summary. WHEN TO USE: For pre-computed technical analysis. Returns a bullish/bearish/neutral signal. Use veroq_candles for raw price data instead. RETURNS: Signal summary (signal + bul...
AI agents call veroq_technicals 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 tool is a pure data retrieval/query function that reads and returns technical analysis metrics (RSI, MACD, Bollinger Bands, moving averages, signal summaries) for a given ticker. It has no side effects, does not modify data, execute code, delete records, or move money. The 'signal' it returns is a classification label (bullish/bearish/neutral), not a trading execution or financial obligation.
From the tool's definition Tool description states it 'Get[s] all major technical indicators' and 'Returns: Signal summary...and full indicator values.' No write, delete, execute, or financial transaction capabilities are mentioned. It retrieves pre-computed technical analysis data.
Attacks that exploit this kind of access
Get all major technical indicators for a ticker: RSI, MACD, Bollinger Bands, moving averages, and overall signal summary. WHEN TO USE: For pre-computed technical analysis. Returns a bullish/bearish/neutral signal. Use veroq_candles for raw price data instead. RETURNS: Signal summary (signal + bullish/bearish/neutral counts) and full indicator values (RSI, MACD, BBands, SMA, EMA). 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_technicals: 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_technicals 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_technicals 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_technicals. 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_technicals 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 →