Get the full profile for a ticker — price, fundamentals, technicals, sentiment, and recent news in one call. WHEN TO USE: For a complete data dump on a single ticker. 9 sources in parallel. Use veroq_ticker_analysis for an interpreted analysis instead. RETURNS: Price data, fundamentals, technical...
AI agents call veroq_full 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.
veroq_full retrieves and aggregates market data (price, fundamentals, technicals, sentiment, news) from 9 sources in parallel. It performs no writes, deletions, code execution, or financial transactions—only data retrieval. The tool is informational and has no side effects beyond reading existing data. Confidence is high because the description is explicit about the read-only nature of the operation.
From the tool's definition Tool description states it 'Get[s] the full profile for a ticker — price, fundamentals, technicals, sentiment, and recent news in one call' and 'RETURNS: Price data, fundamentals, technical indicators, sentiment scores, and recent news briefs.' These are all…
Attacks that exploit this kind of access
Get the full profile for a ticker — price, fundamentals, technicals, sentiment, and recent news in one call. WHEN TO USE: For a complete data dump on a single ticker. 9 sources in parallel. Use veroq_ticker_analysis for an interpreted analysis instead. RETURNS: Price data, fundamentals, technical indicators, sentiment scores, and recent news briefs. 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_full: 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_full 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_full 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_full. 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_full 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 →