The most important tool — ask any question in natural language and get verified intelligence. WHEN TO USE: This should be your DEFAULT tool for any financial, market, or economic question. It automatically detects 41 intents (price, technicals, earnings, sentiment, screener, backtest, competitors...
AI agents call veroq_ask 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.
Despite the high-severity financial domain context, veroq_ask is a Read operation—it queries financial and market data sources and returns structured information and summaries. It does not execute trades, move money, create/modify data, or delete anything.
From the tool's definition Tool description states it 'ask[s] any question in natural language and get[s] verified intelligence' and 'RETURNS: Structured data from all matched endpoints + LLM-generated natural language summary + composite trade signal'.
Attacks that exploit this kind of access
The most important tool — ask any question in natural language and get verified intelligence. WHEN TO USE: This should be your DEFAULT tool for any financial, market, or economic question. It automatically detects 41 intents (price, technicals, earnings, sentiment, screener, backtest, competitors, insider, filings, analysts, congress, crypto, forex, economy, and more) and routes to the right data sources. Use this FIRST before reaching for specialized tools. RETURNS: Structured data from all matched endpoints + LLM-generated natural language summary + composite trade signal (0-100) + confidence level (high/medium/low) + follow-up suggestions. COST: 1-5 credits depending on endpoints hit. Responses cached 60s for ticker queries, 30s for general. Use fast=true to skip LLM summary and save ~2 seconds. EXAMPLES:. 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_ask: 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_ask 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_ask 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_ask. 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_ask 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 →